Setting up Amazon Elastic Beanstalk app under VPC
amazon-elastic-beanstalk, amazon-vpc, amazon-web-services
Solution
This is almost certainly an issue with not being able to communicate with the NAT. The documentation is a little ambiguous when it comes to configuring your `.ebextensions` config files.
- Don't mess with the Network ACLs for the VPC. The infrastructure needs to be able to talk to itself.
- The NAT instance & Beanstalk ELB need to be in the Public subnet (10.0.0.0/24)
- The Beanstalk instances themselves need to be in the Private subnet (10.0.1.0/24)
- The Security Group that you apply to the instances needs to also apply to the NAT. That Security Group also needs to be on its own Inbound list so that everything inside that SG can talk to each other.
- Using `curl`, try to make outbound calls. First on the Bastion Host, then on the NAT, then on a Beanstalk instance. Are any of them unable to make outbound calls?
I just recently spent a couple of weeks trying to develop a CloudFormation template that handles this stuff. I think that most of it is still in my brain. I think.
If these troubleshooting steps don't help, let me know and I'll dig a little deeper.
Problem
I've created a new environment for my beanstalk app under a vpc. I created a vpc with private and public subnets. I've configured the security groups as outlined here: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/AWSHowTo-vpc-basic.html The environment seemed to setup correctly but the status is red. Clicking on monitor reveals no data for latency or requests. The website url returns error code 503. Not sure what to do