4

For a new web application I am looking at AWS ElasticBeanstalk.

I like its auto-balancing and auto-rolling updates' system as well as all the other scaling-related features.

But.. I need a static IP in order to communicate with a webservice api.

What would be the optimal solution here?

  • skip EB to manual ec2 with balancers
  • EB in VPC with frontier elastic IP
  • avoid AWS altogether
  • something else
Improve this question

1 Answer 1

Reset to default
9

You can use Elastic Beanstalk along with a VPC for your scenario.

  1. Use a VPC with public and private subnets.
  2. Add a NAT to a public subnet and give it an Elastic IP address.
  3. Ensure all traffic from the private subnets goes through your NAT.
  4. Create your Elastic Beanstalk application, placing the ELB in a public subnet and the EC2 instances in one or more private subnets.

All incoming traffic will hit your ELB and funnel to your EC2 instances. When your EC2 instances access the web service API, traffic will go through the NAT, thus appearing to originate from the static IP address.

Improve this answer
1
  • We had the same question / issue except we needed to get to both an API and a database (not living in AWS). Testing this out now, but it looks like it will be EXACTLY what we needed.
    – Jay Stevens
    Sep 5, 2015 at 21:26

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .