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.

Load Balancer for Your AWS Elastic Beanstalk Environment

When you enable load balancing, AWS Elastic Beanstalk creates an Elastic Load Balancing load balancer for your environment. The load balancer distributes traffic among your environment's instances.

Elastic Beanstalk supports these load balancer types:

  • Classic Load Balancer – The Elastic Load Balancing previous-generation load balancer. Routes HTTP, HTTPS, or TCP request traffic to different ports on environment instances.

  • Application Load Balancer – An application layer load balancer. Routes HTTP or HTTPS request traffic to different ports on environment instances based on the request path.

  • Network Load Balancer – A network layer load balancer. Routes TCP request traffic to different ports on environment instances. Supports both active and passive health checks.

By default, Elastic Beanstalk creates a Classic Load Balancer for your environment. It configures the load balancer to listen for HTTP traffic on port 80 and forward this traffic to instances on the same port. You can choose the type of load balancer that your environment uses only during environment creation. You can change settings to manage the behavior of your running environment's load balancer, but you can't change its type.

The Elastic Beanstalk console supports creating and managing an Elastic Beanstalk environment with either a Classic Load Balancer or an Application Load Balancer. You can create and manage environments with all load balancer types using the EB CLI eb create command, the Elastic Beanstalk APIs, or configuration files (.ebextensions).

We provide a topic for each Elastic Beanstalk-supported load balancer type that describes its functionality and how to configure and manage it in an Elastic Beanstalk environment. You can also configure a load balancer to upload access logs to Amazon S3. See the following: