An organization is planning to host a WordPress blog as well a joomla CMS on a single instance
launched with VPC. The organization wants to have separate domains for each application and
assign them using Route 53. The organization may have about ten instances each with two
applications as mentioned above. While launching the instance, the organization configured two
separate network interfaces (primary + ENI) and wanted to have two elastic IPs for that instance.
It was suggested to use a public IP from AWS instead of an elastic IP as the number of elastic
IPs is restricted. What action will you recommend to the organization?
A.
I agree with the suggestion but will prefer that the organization should use separate subnets with
each ENI for different public IPs.
B.
I do not agree as it is required to have only an elastic IP since an instance has more than one ENI
and AWS does not assign a public IP to an instance with multiple ENIs.
C.
I do not agree as AWS VPC does not attach a public IP to an ENI; so the user has to use only an
elastic IP only.
D.
I agree with the suggestion and it is recommended to use a public IP from AWS since the
organization is going to use DNS with Route 53.
Explanation:
A Virtual Private Cloud (VPC) is a virtual network dedicated to the user’s AWS account. It enables
the user to launch AWS resources into a virtual network that the user has defined. An Elastic
Network Interface (ENI) is a virtual network interface that the user can attach to an instance in a
VPC. The user can attach up to two ENIs with a single instance. However, AWS cannot assign a
public IP when there are two ENIs attached to a single instance. It is recommended to assign an
elastic IP in this scenario. If the organization wants more than 5 EIPs they can request AWS to
increase the number.
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html
b