Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

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

by | Jun 29, 2021

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:

failed to communicate with AWS Elastic Beanstalk


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:

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

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:

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 (
  • Amazon Simple Storage Service (Amazon S3)

[Need assistance? We can help you]


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


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.