AWS Elastic Beanstalk
Developer Guide
AWS services or capabilities described in AWS documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon AWS.

Deploying Elastic Beanstalk Applications from Docker Containers

Elastic Beanstalk supports the deployment of web applications from Docker containers. With Docker containers, you can define your own runtime environment. You can choose your own platform, programming language, and any application dependencies (such as package managers or tools), that aren't supported by other platforms. Docker containers are self-contained and include all the configuration information and software your web application requires to run. All environment variables defined in the Elastic Beanstalk console are passed to the containers.

By using Docker with Elastic Beanstalk, you have an infrastructure that automatically handles the details of capacity provisioning, load balancing, scaling, and application health monitoring. You can manage your web application in an environment that supports the range of services that are integrated with Elastic Beanstalk, including but not limited to VPC, RDS, and IAM. For more information about Docker, including how to install it, what software it requires, and how to use Docker images to launch Docker containers, go to Docker: the Linux container engine.


If a Docker container running in an Elastic Beanstalk environment crashes or is killed for any reason, Elastic Beanstalk restarts it automatically.

The topics in this chapter assume some knowledge of Elastic Beanstalk environments. If you haven't used Elastic Beanstalk before, try the getting started tutorial to learn the basics.

Docker Platform Configurations

The Docker platform for Elastic Beanstalk has two generic configurations (single container and multicontainer), and several preconfigured containers.

Single Container Docker

The single container configuration can be used to deploy a Docker image (described in a Dockerfile or definition) and source code to EC2 instances running in an Elastic Beanstalk environment. Use the single container configuration when you only need to run one container per instance.

For samples and help getting started with a single container Docker environment, see Single Container Docker Environments. For detailed information on the container definition formats and their use, see Single Container Docker Configuration.

Multicontainer Docker

The other basic configuration, Multicontainer Docker, uses the Amazon Elastic Container Service to coordinate a deployment of multiple Docker containers to an Amazon ECS cluster in an Elastic Beanstalk environment. The instances in the environment each run the same set of containers, which are defined in a file. Use the multicontainer configuration when you need to deploy multiple Docker containers to each instance.

For more details on the Multicontainer Docker configuration and its use, see Multicontainer Docker Environments. The Multicontainer Docker Configuration topic details version 2 of the format, which is similar to but not compatible with the version used with the single container configuration. There is also a tutorial available that guides you through a from scratch deployment of a multicontainer environment running a PHP website with an nginx proxy running in front of it in a separate container.

Preconfigured Docker Containers

In addition to the two generic Docker configurations, there are several preconfigured Docker platform configurations that you can use to run your application in a popular software stack such as Java with Glassfish or Python with uWSGI. Use a preconfigured container if it matches the software used by your application.

For more information, see Preconfigured Docker Containers.