How can I resolve the error I get when my Amazon EC2 instances fail to communicate with Elastic Beanstalk?
Last updated: 2019-10-11
When I try to create an Elastic Beanstalk environment, I get the following error: "The EC2 instances failed to communicate with AWS Elastic Beanstalk, either because of configuration problems with the VPC or a failed EC2 instance. Check your VPC configuration and try launching the environment again." How can I resolve this error?
You will receive this error if your Amazon Elastic Compute Cloud (Amazon EC2) instances aren't configured to initiate outbound connections to your Elastic Beanstalk service over the internet. Your instances must have access to the internet through either a public subnet or private subnet.
- Verify that the network ACL associated with your subnets allows outbound connections to the internet (for example, 0.0.0.0/0).
- If you select a custom Amazon Virtual Private Cloud (Amazon VPC) when you created your Elastic Beanstalk environment, choose the appropriate subnets for instance and load balancer visibility.
- If your EC2 instances are in a public subnet, verify that the route table has a route to the internet (for example, 0.0.0.0/0) through an internet gateway.
- If your EC2 instances are in a private subnet, verify that the route table associated with the NAT gateway or the NAT instance has a route to the internet (for example, 0.0.0.0/0).
Note: Your NAT gateway or NAT instance must be in a public subnet to communicate with the internet.