What Is ELB?
Elastic Load Balance (ELB) automatically distributes incoming traffic across multiple backend servers based on the listening rules you configure. ELB expands the service capabilities of your applications and improves their availability by eliminating single points of failure (SPOFs).
ELB consists of the following components:
- Load balancer: distributes incoming traffic across backend servers in one or more availability zones (AZs).
- Listener: uses the protocol and port you specify to check for requests from clients and route the requests to associated backend servers based on the listening rules and forwarding policies you configure. You can add one or more listeners to a load balancer.
- Backend server group: contains one or more backend servers to receive requests routed by the listener. You need to add at least one backend server to a backend server group.
You can also configure health checks for a backend server group to check the health of each backend server. When a backend server is unhealthy, the load balancer stops routing new requests to this server.
Load Balancer Types
ELB provides the following types of load balancers.
- Dedicated load balancers have exclusive use of underlying resources, so that the performance of a dedicated load balancer is not affected by other load balancers. In addition, there are a wide range of specifications available for selection.
Dedicated load balancers are in the open beta test in CN-Hong Kong, AP-Bangkok, AP-Singapore, and LA-Sao Paulo1.
- Shared load balancers are deployed in clusters and share underlying resources, so that the performance of a load balancer is affected by other load balancers. Shared load balancers were previously named enhanced load balancers.
For details, see Differences Between Dedicated and Shared Load Balancers.
You can use either of the following methods to access ELB:
You can call APIs to access ELB. For details, see the Elastic Load Balance API Reference.