AWS Elastic Beanstalk
Developer Guide (API Version 2010-12-01)


This section provides a table of the most common Elastic Beanstalk issues and how to resolve or work around them.

Issue Workaround
Unable to connect to Amazon RDS from Elastic Beanstalk. To connect RDS to your Elastic Beanstalk application, do the following:
  • Make sure RDS is in the same Region as your Elastic Beanstalk application.

  • Make sure the RDS security group for your instance has an authorization for the Amazon EC2 security group you are using for your Elastic Beanstalk environment. For instructions on how to find the name of your EC2 security group using the AWS Management Console, see Security Groups. For more information about configuring your EC2 security group, go to the "Authorizing Network Access to an Amazon EC2 Security Group" section of Working with DB Security Groups in the Amazon Relational Database Service User Guide.

  • For Java, make sure the MySQL JAR file is in your WEB-INF/lib. See Adding an Amazon RDS DB Instance to Your Java Application Environment for more details.

Experiencing a couple of seconds of downtime when updating the version of my application. Because Elastic Beanstalk uses a drop-in upgrade process, there might be a few seconds of downtime. Use rolling deployments to minimize the effect of deployments on your production environments.
Unable to connect to another Amazon EC2 instance using the Amazon EC2 security group for your Elastic Beanstalk environment. Create a CNAME record and point this to the public DNS of the Amazon EC2 instance.
How can I change my application URL from to Register in a DNS server a CNAME record such as: CNAME
Unable to specify a specific Availability Zone for my Elastic Beanstalk application. You can pick specific AZs using the APIs, CLI, Eclipse plug-in, or Visual Studio plug-in. For instructions about using the AWS Management Console to specify an Availability Zone, see Configuring Auto Scaling with Elastic Beanstalk.
Getting charged for my Elastic Beanstalk application. The default settings for Elastic Beanstalk do not incur any additional charges. However, if you modified the default settings by changing the Amazon EC2 instance type or adding additional Amazon EC2 instance, charges may be accrued. For information about the free tier, see If you have questions about your account, contact our customer service team directly.
How can I receive notifications by SMS? If you specify an SMS email address, such as one constructed on, you will receive the notifications by SMS. To subscribe to more than one email address, you can use the Elastic Beanstalk command line to register an SNS topic with an environment.
How do I change my environment's instance type? In the Web Tier section of the environment configuration screen, choose the gear icon on the Instances card. Select a new instance type and click Apply to update your environment. Elastic Beanstalk will terminate all running instances and replace them with new ones.
Unable to connect to Elastic Beanstalk when deploying using the AWS Toolkit for Eclipse. Try one of the following:
  • Make sure you are running the latest distribution of Eclipse.

  • Make sure you've signed up your account for Elastic Beanstalk (and have received an email confirmation).

  • Check the "Error Log" view in Eclipse to see if there's any additional information or stack traces.

How can I prevent EBS volumes from being deleted when Elastic Beanstalk? Instances in your environment use EBS for storage; however, the root volume is deleted when an instance is terminated by Autoscaling. It is not recommended to store state or other data on your instances. If needed, you can prevent volumes from being deleted with the EC2 CLI: $ ec2-modify-instance-attribute -b '/dev/sdc=<vol-id>:false as described in the EC2 Command Line Reference.
Servers that were created in the AWS Management Console do not appear in the Toolkit for Eclipse You can manually import servers by following the instructions at Importing Existing Environments into Eclipse.
Environments are launched, but with command timeout errors Your application may take a long time to deploy if you use configuration files that run commands on the instance, download large files, or install packages. Make sure that your commands or scripts return properly and increase the command timeout if necessary. For more information, see Launch and Update Environment Operations Succeeded but with Command Timeouts.
Unable to update an environment with event You cannot configure an AWS Elastic Beanstalk environment with values for both the Elastic Load Balancing Target option and Application Healthcheck URL option

This indicates that, Elastic Beanstalk received an option setting that conflicts with the value you provided for the Application Healthcheck URL option setting in the aws:elasticbeanstalk:application namespace. Remove the Target option (in the aws:elb:healthcheck namespace) from environment or configuration file and then try updating your environment again.

Update failed with reason ELB cannot be attached to multiple subnets in the same AZ. when attempting to move a load balancer between subnets within an AZ.

Changing subnets on the load balancer requires moving it out of the original availability zone(s) and then back into the original with the desired subnets. During the process, all of your instances will be migrated between AZs, causing significant downtime. If you need to use different subnets, it's better just to create a new environment and perform a CNAME swap.