Q: I am using the Amazon Cloud Licensing Service and need to understand how to configure this
environment when using PCC.
Terms that need to be defined:
ENI - Elastic Network Interface (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-
eni.html): Defines properties of a Network Interface (e.g. MAC Address) which can be attached to a
single EC2 instance. The ENI is independent of EC2 instances, but can be attached to any one instance at
a time. ENI's can only be attached to EC2 instances that are within an Amazon VPC. There is no cost
associated with an ENI.
VPC - Virtual Private Cloud
(http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Introduction.html): A virtual network
defined by the user, but within the Amazon AWS cloud. There is no charge for the VPC, unless a
hardware VPN connection is established with it, in which case there is a charge per hour of the
connection. With some VPC scenarios EC2 instances are assigned only private IPs (can't be accessed over
the internet). So, if an EC2 instance in a VPC needs to be accessed directly from the internet, an Elastic IP
needs to be associated with the ENI to do so. Elastic IPs are free, however, but limited to only 5 per
account. Also, if you create an EIP that is NOT assigned to anything, there is a nominal charge to
discourage that (since IPs are limited in IPv4).
The steps to setup this infrastructure are:
1. Create a VPC (http://docs.aws.amazon.com/AmazonVPC/latest/GettingStartedGuide/Wizard.html).
There is no charge for this as long as Hardware VPN connections are not created for it.
2. Launch an Instance into VPC
(http://docs.aws.amazon.com/AmazonVPC/latest/GettingStartedGuide/LaunchInstance.html)
3. (Optional) Assign Elastic IP
(http://docs.aws.amazon.com/AmazonVPC/latest/GettingStartedGuide/EIP.html. This is only required if
access to the instance is required from the public internet. Alternatively, NAT Instances
(http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_NAT_Instance.html) can a