AWS Elastic Beanstalk
Developer Guide (API Version 2010-12-01)
AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.

Environment Types

In Elastic Beanstalk, you can create a load-balancing, autoscaling environment or a single-instance environment. The type of environment that you require depends on the application that you deploy. For example, you can develop and test an application in a single-instance environment to save costs and then upgrade that environment to a load-balancing, autoscaling environment when the application is ready for production.


A worker environment tier for a web application that processes background tasks does not include a load balancer. However, a worker environment does effectively scale out by adding instances to the autoscaling group to process data from the Amazon SQS queue when the load necessitates it.

Load-balancing, Autoscaling Environment

A load-balancing and autoscaling environment uses the Elastic Load Balancing and Auto Scaling services to provision the Amazon EC2 instances that are required for your deployed application. Auto Scaling automatically starts additional instances to accommodate increasing load on your application. If the load on your application decreases, Auto Scaling stops instances but always leaves your specified minimum number of instances running. If your application requires scalability with the option of running in multiple Availability Zones, use a load-balancing, autoscaling environment. If you're not sure which environment type to select, you can pick one, and if required, switch the environment type later.

Single-instance Environment

A single-instance environment contains one Amazon EC2 instance with an Elastic IP address. A single-instance environment doesn't have a load balancer, which can help you reduce costs compared to a load-balancing, autoscaling environment. Although a single-instance environment does use the Auto Scaling service, settings for the minimum number of instances, maximum number of instances, and desired capacity are all set to 1. Consequently, new instances are not started to accommodate increasing load on your application.

Use a single-instance environment if you expect your production application to have low traffic or if you are doing remote development. If you're not sure which environment type to select, you can pick one, and, if required, you can switch the environment type later. For more information, see Changing Environment Type.

Changing Environment Type

You can change your environment type to a single-instance or load-balancing, autoscaling environment by editing your environment's configuration. In some cases, you might want to change your environment type from one type to another. For example, let's say that you developed and tested an application in a single-instance environment in order to save costs. When your application is ready for production, you can change the environment type to a load-balancing, autoscaling environment so that it can scale to meet the demands of your customers.

To change an environment's type

  1. Open the Elastic Beanstalk console.

  2. Navigate to the management page for your environment.

  3. Choose Configuration.

  4. Click 
            for the Scaling settings.

  5. In the Environment Type section, select the type of environment that you want.

  6. If your environment is in a VPC, select subnets to place ELB and EC2 instances in. Each availability zone that your application runs in must have both. See Using Elastic Beanstalk with Amazon VPC for details.

  7. Click Save.

    Note that it can take several minutes for the environment to update while Elastic Beanstalk provisions AWS resources.