Creating a Dedicated Load Balancer

Scenarios

You have prepared everything required for creating a load balancer. For details, see Preparations for Creating a Load Balancer.

Constraints

• After a load balancer is created, the VPC cannot be changed. If you want to change the VPC, create a load balancer and select a different VPC.
• To ping the IP address of a load balancer, you need to add a listener to it.

Procedure

1. Log in to the management console.
2. In the upper left corner of the page, click and select the desired region and project.
3. Hover on in the upper left corner to display Service List and choose Network > .
4. On the Load Balancers page, click Create Elastic Load Balancer. Complete the basic configurations based on Table 1.

   Table 1 Parameters for configuring the basic information

   Parameter	Description	Example Value
   Region	Specifies the desired region. Resources in different regions cannot communicate with each other over internal networks. For lower network latency and faster access to resources, select the nearest region.	-
   AZ	Specifies the AZ of the load balancer. You can deploy a load balancer in multiple AZs for high availability. If an AZ becomes faulty or unavailable, the load balancers in other AZs can route requests to backend servers to ensure service continuity and improve application reliability. NOTE: If you change the AZs of an existing load balancer, the load balancer may fail to route requests for several seconds. It is recommended that you plan the AZs in advance, or change the AZs during off-peak hours when necessary.	-
   Name	Specifies the load balancer name.	elb-test
   Description	Provides supplementary information about the load balancer.	-

   Table 2 Tag naming rules

   Item	Requirement	Example Value
   Tag key	Cannot be empty. Must be unique for the same load balancer. Can contain a maximum of 36 characters.	elb_key1
   Tag value	Can contain a maximum of 43 characters.	elb-01

5. Configure the network parameters based on Table 3.

   Table 3 Parameters for network configurations

   Parameter	Description	Example Value
   Network Type	Specifies the network where the load balancer works. You can select one or more network types. Public IPv4 network: The load balancer routes requests from the clients to backend servers over the Internet. Private IPv4 network: The load balancer routes requests from the clients to backend servers in a VPC. IPv6 network: An IPv6 address will be assigned to the load balancer to route requests from IPv6 clients. NOTE: If you do not select any of the options, the load balancer cannot communicate with the clients after it is created. When you are using ELB or testing network connectivity, ensure that the load balancer has a public or private IP address bound.	Public IPv4 network
   VPC	Specifies the VPC where the load balancer works. Select an existing VPC or create a new one. For more information about VPC, see the Virtual Private Cloud User Guide.	vpc-test
   Frontend Subnet	Specifies the subnet where the load balancer will work. The system assigns IP addresses to load balancers for receiving requests based on the configured network type. IPv4 private network: assigns IPv4 private addresses. IPv6 network: assigns IPv6 private or public addresses. NOTE: If you select IPv6 network for Network Type and the selected VPC does not have any subnet that supports IPv6, enable IPv6 for the subnets or create a subnet that supports IPv6. For details, see the Virtual Private Cloud User Guide.	subnet-test
   Backend Subnet	The load balancer uses the IP addresses in the backend subnet to forward requests to the backend servers. Select Subnet of the load balancer by default. Select an existing subnet in the VPC where the load balancer works. Add a new subnet NOTE: The number of IP addresses required depend on the specifications, number of AZs, and IP as a backend function you have configured when you create the load balancer. The actual number of occupied IP addresses depends on that displayed on the console. An application load balancer requires 8 to 30 additional IP addresses in the backend subnet for traffic forwarding. The actual number of required IP addresses depends on the ELB cluster size. If load balancers are deployed in the same cluster and work in the same backend subnet, they share the same IP addresses to save resources.	Subnet of the load balancer
   Private IPv4 network configuration
   IPv4 Address	Specifies how you want the IPv4 address to be assigned. Automatically assign IP address: The system automatically assigns an IPv4 address to the load balancer. Manually specify IP address: Manually specify an IPv4 address to the load balancer. NOTE: Network ACL rules configured for the backend subnet of the load balancer will not restrict the traffic from the clients to the load balancer. If these rules are configured, the clients can directly access the load balancer. To control access to the load balancer, configure access control for all listeners added to the load balancer. For details, see Access Control.	Automatically assign IP address
   IPv6 network configuration
   IPv6 Address	Specifies how you want the IPv6 address to be assigned. NOTE: Network ACL rules configured for the backend subnet of the load balancer will not restrict the traffic from the clients to the load balancer. If network ACL rules are configured, the clients can directly access the load balancer. To control access to the load balancer, configure access control for all listeners added to the load balancer. For details, see Access Control.	Automatically assign IP address
   Shared Bandwidth	Specifies the shared bandwidth that the IPv6 address will be added to. You can choose not to select a shared bandwidth, select an existing shared bandwidth, or assign a shared bandwidth.	Skip
   Public IPv4 network configuration
   EIP	This parameter is mandatory when Network Type is set to IPv4 public network. New EIP: The system will assign a new EIP to the load balancer. Use existing: Select an existing IP address.	-
   EIP Type	Specifies the link type (BGP) when a new EIP is used. Dynamic BGP: When changes occur on a network using dynamic BGP, routing protocols provide automatic, real-time optimization of network configurations, ensuring network stability and optimal user experience.	Dynamic BGP
   Billed By	Specifies how the bandwidth will be billed. You can select Bandwidth, Traffic, or Shared Bandwidth. Bandwidth: You specify the maximum bandwidth and pay for the amount of time you use the bandwidth. Traffic: You specify a maximum bandwidth and pay for the outbound traffic you use. Shared Bandwidth	Shared Bandwidth
   Bandwidth	Specifies the maximum bandwidth.	100 Mbit/s

6. Confirm the configuration and submit your request.