Automatically distribute your incoming application traffic across multiple Amazon EC2 instances
With Elastic Load Balancing, you can add and remove EC2 instances as your needs change without disrupting the overall flow of information. If one EC2 instance fails, Elastic Load Balancing automatically reroutes the traffic to the remaining running EC2 instances. If the failed EC2 instance is restored, Elastic Load Balancing restores the traffic to that instance. Elastic Load Balancing offers clients a single point of contact, and it can also serve as the first line of defense against attacks on your network. You can offload the work of encryption and decryption to Elastic Load Balancing, so your servers can focus on their main task.
Why people like AWS Elastic Load Balancing (ELB)
Add a one-liner

Companies using AWS Elastic Load Balancing (ELB)
AWS Elastic Load Balancing (ELB) integrates with

AWS Elastic Load Balancing (ELB)'s Features
  • Distribution of requests to Amazon EC2 instances (servers) in multiple Availability Zones so that the risk of overloading one single instance is minimized. And if an entire Availability Zone goes offline, Elastic Load Balancing routes traffic to instances in other Availability Zones.
  • Continuous monitoring of the health of Amazon EC2 instances registered with the load balancer so that requests are sent only to the healthy instances. If an instance becomes unhealthy, Elastic Load Balancing stops sending traffic to that instance and spreads the load across the remaining healthy instances.
  • Support for end-to-end traffic encryption on those networks that use secure (HTTPS/SSL) connections.
  • The ability to take over the encryption and decryption work from the Amazon EC2 instances, and manage it centrally on the load balancer.
  • Support for the sticky session feature, which is the ability to "stick" user sessions to specific Amazon EC2 instances.
  • Association of the load balancer with your domain name. Because the load balancer is the only computer that is exposed to the Internet, you don’t have to create and manage public domain names for the instances that the load balancer manages. You can point the instance's domain records at the load balancer instead and scale as needed (either adding or removing capacity) without having to update the records with each scaling activity.
  • When used in an Amazon Virtual Private Cloud (Amazon VPC), support for creation and management of security groups associated with your load balancer to provide additional networking and security options.
  • Supports use of both the Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6).

Explore other Build, Test, Deploy tools that are known for: