Stuck with the “Failed to communicate with AWS Elastic Beanstalk” error? We can help you.

Often AWS users report to us that they get this error while trying to create an AWS Elastic Beanstalk environment.

Here at Bobcares, we handle requests from our customers to fix similar errors as a part of our Server Management Services.

Today we will see how our Support Engineers fix this for our customers.

How to fix “Failed to communicate with AWS Elastic Beanstalk”

Before going into the steps for fixing this error we can see what causes this error.

A typical error looks like the one given below:

Cause:

We receive this error when our Amazon Elastic Compute Cloud (Amazon EC2) instances aren’t configured to initiate outbound connections to Elastic Beanstalk and other service endpoints.

The instances must have access to these endpoints through either a public subnet, private subnet, or Amazon Virtual Private Cloud (Amazon VPC) endpoints.

Steps to fix this error

1. First, we need to verify that the network ACL associated with subnets allows outbound connections to the internet. For example: 0.0.0.0/0

2. If we choose a custom Amazon VPC while creating the Elastic Beanstalk environment, we must choose the appropriate subnets for instance, and load balancer visibility.

3. Then we must verify that the route table has a route to the internet through an internet gateway if theEC2 instance is in a public subnet. For example 0.0.0.0/0

4. In case if it is in a private subnet, we must 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

5. After that we need to verify that the attributes enableDnsHostnames and enableDnsSupport are enabled in the VPC where the Elastic Beanstalk environment is launched.

6. And if the Elastic Beanstalk environment is using VPC endpoints, we must set up the following endpoints to launch the environment properly:

• Amazon Simple Queue Service (Amazon SQS)
• AWS CloudFormation
• Elastic Beanstalk (com.amazonaws.your-region.elasticbeanstalk)
• Elastic Beanstalk health (elasticbeanstalk-health.your-region.amazonaws.com)
• Amazon Simple Storage Service (Amazon S3)

[Need assistance? We can help you]

Conclusion

To conclude, we saw the steps that our Support Techs follow to fix this error for our customers.