An Edge Load Balancer (ELB) instance distributes client traffic to backend servers, which are ENS instances, based on forwarding rules. To use the edge load balancing service, you must create an ELB instance and add listeners and backend servers.
Prerequisites
-
Plan the region for the ELB instance. Because load balancing does not support deployment across different edge zones, you must ensure that your ELB instance and ENS instances are in the same region.
-
Create a custom virtual network and a vSwitch. You must deploy the ELB instance in this network.
Create the instance
-
Log on to the ENS console.
-
In the navigation pane on the left, choose .
-
On the ELB Instance page, click Create Instance.
-
On the Edge Load Balancer page, configure the instance as follows.
Parameter
Description
Billing Method
Only Pay-as-you-go is supported.
Instance Name
Enter a custom name for the ELB instance.
Region
Select a region for the instance. Make sure the ELB instance is in the same region as the backend ENS servers.
Network
Select your custom virtual network.
vSwitch
Select your custom vSwitch.
Instance Type
Select the specifications based on your business scenario. Estimate the maximum number of concurrent connections and Queries Per Second (QPS) that the load balancer must handle. For more information about the performance metrics for different specifications, see Instance specifications.
-
Select the Terms of Service checkbox, and then click Confirm.
What to do next
-
Configure a listener for the instance. The listener checks for connection requests and distributes them to backend servers based on the scheduling algorithm. For more information, see Configure a listener.
-
By default, ELB instances created in the ENS console are private and do not provide public network access. To enable load balancing for traffic from the public network, you must associate an Elastic IP Address (EIP) with the ELB instance. For more information, see Associate an EIP.