Creating a Dedicated Load Balancer

Scenario

Notes and 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 dedicated 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. Click in the upper left corner to display Service List and choose Network > Elastic Load Balance.
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
   Type	Specifies the type of the load balancer. The type cannot be changed after the load balancer is created. Dedicated load balancers work well for heavy-traffic and high-concurrency workloads, such as large websites, cloud native applications, IoV, and multi-AZ disaster recovery applications.
   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. An AZ is a part of a region and has its own independent power supplies and networks. AZs are physically isolated but interconnected through an internal network. You can select multiple AZs for a load balancer to ensure high availability. If the load balancer in an AZ goes down, the load balancer in another AZ can route requests to backend servers to ensure service continuity and improve application reliability. For details about AZ planning, see AZ. If you select multiple AZs for a load balancer, its performance, such as the number of new connections and the number of concurrent connections, will multiply by the number of AZs. For example, a dedicated load balancer in an AZ can handle 20 million concurrent connections. If you select two AZs for a dedicated load balancer, it can handle up to 40 million concurrent connections.
   Specifications	Elastic specifications work well for fluctuating traffic, and you will be charged for how many LCUs you use. Fixed specifications are suitable for stable traffic, and you will be charged for the specifications you select. Select either Application load balancing (HTTP/HTTPS) or Network load balancing (TCP/UDP) or both, and then select the desired specification. You can select only one specification for Application load balancing (HTTP/HTTPS) and Network load balancing (TCP/UDP), respectively.
   Name	Specifies the load balancer name. The name can contain: 1 to 64 characters. Letters, digits, underscores (_), hyphens (-), and periods (.).
   Enterprise Project	Specifies an enterprise project by which cloud resources and members are centrally managed.
   Description	Provides supplementary information about the load balancer.
   Tag	Identifies load balancers so that they can be easily found. A tag consists of a tag key and a tag value. The tag key marks a tag, and the tag value specifies specific tag content. For details about the naming rules, see Table 2. A maximum of 20 tags can be added.

   Table 2 Tag naming rules

   Parameter	Rule
   Tag key	Cannot be empty. Must be unique for the same load balancer. Can contain a maximum of 36 characters. Can contain only letters, digits, underscores (_), hyphens (-), at signs (@) are allowed.
   Tag value	Can contain a maximum of 43 characters. Can contain only letters, digits, underscores (_), hyphens (-), at signs (@).

5. Configure the network parameters based on Table 3.

   Table 3 Parameters for network configurations

   Parameter	Description
   IP as a Backend	Specifies whether to associate backend servers that are not in the VPC of the load balancer. After this function is enabled, you can associate the backend servers with the load balancer by using their IP addresses. NOTE: To use this function, you need to configure correct VPC routes to ensure requests can be routed to backend servers. If you enable this option, more IP addresses in the backend subnet will be reserved for the load balancer to communicate with backend servers. Ensure that the selected subnet has sufficient IP addresses. After you select a subnet, you can view the number of IP addresses required by the load balancer in the infotip.
   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 IPv4 requests from the clients to backend servers over the Internet. Private IPv4 network: The load balancer routes IPv4 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.
   VPC	Specifies the VPC where the dedicated load balancer will work. You cannot change the VPC after the load balancer is created. Plan the VPC as required. Select an existing VPC, or click View VPCs to create a desired one For more information about VPC, see the Virtual Private Cloud User Guide.
   Frontend Subnet	Specifies the frontend subnet from which an IP address will be assigned to the load balancer to receive client requests. After a load balancer is created, you can unbind the IP address from it and assign an IP address from a new frontend subnet to the load balancer. The system assigns IP addresses in this subnet 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.
   Backend Subnet	Specifies the backend subnet from which an IP address will be assigned to the load balancer to forward requests to backend servers. Subnet of the load balancer is selected by default. Select an existing subnet in the VPC where the load balancer works. Create a new subnet. NOTE: If you do not enable IPv6 for the specified backend subnet when you create a dedicated load balancer, the load balancer cannot use IPv6 addresses to route requests. The number of IP addresses required depends on the specifications, number of AZs, and IP as a backend function you have configured when you create the load balancer. See the number of occupied IP addresses 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.
   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: You need to manually specify an IPv4 address for the load balancer. NOTE: Network ACL rules configured for the frontend subnet of a load balancer do not restrict traffic from clients to the load balancer. Use access control to limit which IP addresses can access the load balancer. For details, see What Is Access Control?
   IPv6 network configuration
   IPv6 Address	Specifies how you want the IPv6 address to be assigned. Automatically assign IP address: The system automatically assigns an IPv6 address to the load balancer. Manually specify IP address: You need to manually specify an IPv6 address for 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 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 What Is Access Control?
   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.
   Public IPv4 network configuration
   EIP	Specifies the EIP that will be bound to the load balancer for receiving and forwarding requests over the Internet. 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 EIP.
   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.
   Billed By	Specifies how the bandwidth will be billed. You can select one from the following options: Bandwidth: You specify the maximum bandwidth and pay for the amount of time you use the bandwidth. Traffic: You specify the maximum bandwidth and pay for the outbound traffic you use. Shared Bandwidth: The bandwidth is suitable for staggered traffic.
   Bandwidth	Specifies the maximum bandwidth.

6. Confirm the configuration and submit your request.

Exporting the Load Balancer List

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. Click in the upper left corner to display Service List and choose Network > Elastic Load Balance.
4. In the upper left corner of the load balancer list, click Export.

   The system will automatically export information about all of your load balancers as an Excel file to a local directory.