Tonido: A Free, Private Cloud And Streaming Media Server | Unixmen

Private Media Server

Server / April 20, 2020

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 .

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 10.0.0.0/16. 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 10.0.0.0, the mask is 255.255.0.0, and the broadcast address to the hosts is 10.0.255.255.

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:

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.

Important: If 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.

The AMS instance is now ready to use for streaming.

The above article is about creating a Virtual Private Cloud for Adobe Media Server instance on Amazon Web Services with a functional network configurations. For a detailed explanation on VPC and Adobe Media Server, read Amazon virtual private cloud guide and Adobe Media Server help, respectively.

Source: www.adobe.com