Prerequisite knowledge
How to create and launch an instance of
AMS on Amazon web services (AWS).
User level
Required products
Adobe Media Server is a tool that provides live and on-demand streaming to the users using Flash Player and Adobe AIR applications, as well as on Apple iOS devices. Amazon Web Services is a collection of remote computing services now hosting Adobe media server to deliver streaming with low costs and maintenance.
To know the benefits of AMS running on AWS, read this overview.
Why VPC?
A Virtual Private Cloud (VPC) is required when you want to communicate within your network but remain isolated from the public network. Inside a VPC you can completely control your networking environment, including selection of IP address range, creation of subnets, and configuration of route tables and network gateways.
A use case of AMS on VPC can be a public-facing subnet for your servers that has access to the Internet with the backend systems such as databases or application servers on a private subnet with no Internet access.
This article is written for use of AMS on Amazon's VPC offering. To know more about Amazon VPC, see
Defining the terms in an IP addressing scheme
Before you begin deploying AMS in a VPC on AWS, an understanding of the IP addressing and Subnetting is required. A Subnet Mask is a 32-bit combination describing the portion of an IP address that refers to the subnet and the portion that refers to the host. For more information, see
A network Access Control List (ACL) is an optional layer of security that acts as a firewall for controlling traffic in and out of a subnet. One way to set up network ACLs, to add an additional layer of security to your VPC, is to use the rules similar to the rules of your security groups.
The following example illustrates the IP address, Subnet Mask, number of hosts per subnet,  and number of subnets.

Say the subnet block selected for a VPC is In this IP address range the first two octets (16 bits or 2 bytes) are used for subnet and the other two are used for host identification.
The number of subnets are 2^n, where n is the number of borrowed bits from the host. The number of hosts per subnet are 2^h – 2, where h is the number of host bits. For example, if no bits are borrowed from the host then one subnet and 65536 (2^16-2) hosts are possible.
The subnet address can be, the mask is, and the broadcast address to the hosts is
Creating VPC on Amazon Web Services
You can create a VPC on AWS using either the wizard provided by Amazon or manually by using the command console provided by Amazon.
To do a wizard-based VPC setup on AWS, follow these steps:
  1. Login in to your AWS account at
  2. Select Services > All AWS Services > Networking > VPC.
  3. Click on Start VPC Wizard > Select.
    1. Choose IP Classless Inter Domain Routing (CIDR) block. For information on CIDR, see
    2. Choose a unique VPC name.
    3. Select a subnet address for your private network. If required, use the subnet calculator at
    4. Choose Availability Zone. To work with the default for your entire private network, you can continue with the option of No Preference.
    5. Select a unique subnet name.
    6. For DNS Hostnames, click on the Yes radio button. It queries the DNS server on Amazon’s cloud depending on the chosen subnet (Public or Private).
    7. Select the Hardware Tenancy as default. However, if you want the instance to run on a single-tenant hardware, select dedicated.
  4. Click Create VPC.
Setting a VPC manually gives you more control, as the instance can be configured depending on your requirements. Follow these steps to do so:
  1. Login in to your AWS account at
  2. Select Services > All AWS Services > Compute > EC2 > Launch Instance.
  3. On AWS Marketplace, search for Adobe Media Server and select your AMI to start configure your instance.
  4. Create a VPC manually here by following the same steps as above than to have a VPC network configured already via a wizard.
Use Adobe Media Server instance with VPC
  1. Click Services > EC2 > Launch Instance.
  1. Go to AWS Marketplace. Search for Adobe Media Server and select your AMI to start configuring your instance.
  2. Choose an Instance type (hardware specifications).
  1. Configure the following instance details:
    1. Select the number of instances. The default value is 1.
    2. Select a VPC from the network list. Auto-assigned Public IP list and subnet are displayed. Select an associated subnet mask for your network.
    3. Select Enable or Disable for Auto-assign Public IP to override the default setting for the subnet. Availability zone is based on your network selection.
    4. Select the shutdown behavior of an instance.
  1. In add storage, select your instance volume as required.
  2. In the tag instance, provide a name for your instance.
  3. In the configure security group, define the port ranges for each protocol. For more information about ports that are required for AMS to work, see Configure Ports. Below is an example of a security group.
  1. Click Review and Launch and review your configuration settings. Click launch your instance.
  2. Select an existing key pair or create a new key pair for the instance.
  3. To verify that the server is working, stream content using the server. For tutorials on streaming, see on-demand and live streaming.
Assigning a Public IP Address to an AMS instance
ImportantIf you launch an instance in EC2-Classic, it is assigned a public IP address by default. You can't modify this behavior.
In a VPC, all subnets have an attribute that determines whether instances launched into that subnet are assigned a public IP address. By default, no default subnets have this attribute set to false, and default subnets have this attribute set to true. If you launch an instance into a VPC, a public IP addressing feature is available for you to control whether your instance is assigned a public IP address - you can override the default behavior of the subnet's IP addressing attribute. The public IP address is assigned from Amazon's pool of public IP addresses, and is assigned to the network interface with the device index of eth0. This feature depends on certain conditions at the time you launch your instance.