Elastic Load Balancing (ELB) automatically distributes incoming traffic across multiple backend servers based on the listening configurations and forwarding policies. ELB expands the service capabilities of applications and improves application availability by eliminating single points of failure (SPOFs).
ELB now provides two types of load balancers:
For more information, see Differences Between Classic and Enhanced Load Balancers.
Load balancers receive requests from clients and routes the requests to backend servers in one or more availability zones (AZs).
After creating a load balancer, you need to add at least one listener to it. Listeners use the protocol and port that you have configured to check requests from clients and forward the requests to backend servers in a backend server group using the selected the load balancing algorithm. For HTTP and HTTPs listeners, you can configure forwarding policies to route requests based on domain names or URLs.
Backend server groups each uses the protocol and port that you have specified to forward requests to one or more backend servers.
ELB provides the health check function to check the running status of each backend server. When the health check result of a backend server is Abnormal, ELB automatically stops distributing new requests to this server until it recovers.
You can use either of the following methods to access ELB:
A graphical user interface has provided for you. To access the service, log in to the management console and choose All Services > Network > Elastic Load Balancing, or choose Service List > Network > Elastic Load Balancing.
You can also use APIs to send HTTPS requests. This is the most direct way to access ELB. For details, see the Elastic Load Balancing API Reference.