Associating Public IP with EC2 instance with multiple network interfaces

1
votes

I am using Amazon EC2 for my business scenario.

In my scenario I have 3 network interfaces for each EC2 instance (for different purposes): 1 for public access and 2 others for communication inside between instances (This is my solution architecture).

So basically I need one "public IP" for every EC2 instance.

However when creating EC2 instance with multiple network interfaces AWS does not associate public IP address with any one of network interfaces. The only way I found to do so is to create elastic IP and associate this IP with "access" interface of running instance.

When creating an EC2 instance with single network interface this network interface receives public ip address.

The issue is that there is a hard limit of 5 Elastic IPs for VPC, and I'm planning to have totally around 50 instances running simultaneously. Is there any other way to get around this issue, aside from requesting limit increase from AWS?

1
amazon-web-servicesnetworkingamazon-ec2amazon-vpcnetwork-interface
Having a public IP address on so many instances is rarely necessary. Is this not an application that could benefit from NAT Gateways and Elastic Load Balancers? – Michael - sqlbot

1 Answers

2
votes

No, there is no way you can work around.

You can submit an request to AWS Support. They will increase allowed number of EIPs per account upto certain number right away (I couldn't recollect what this number is).

If it crosses certain number, your AWS contact need to involve to get more EIPs.