Creating a Dedicated Load Balancer

Scenarios

You have prepared everything required for creating a dedicated load balancer. For details, see Dedicated Load Balancer Overview.

Notes and Constraints

After a dedicated load balancer is created, its VPC cannot be changed. If you want to change the VPC, create another 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

Go to the Buy Elastic Load Balancer page.

On the load balancer list page, click Buy 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. For details about the differences, see Differences Between Dedicated and Shared Load Balancers.
Billing Mode	Specifies the billing mode of the dedicated load balancer. You are charged for how long you use each load balancer. Pay-per-use: postpaid billing mode. You pay as you go and just pay for what you use. The load balancer usage is calculated by the second but billed every hour.
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 where the dedicated load balancer works. An AZ is a part of a region and has its own independent power supplies and networks. AZs are physically isolated but interconnected through internal networks. 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 routes 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.
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. For details about creating and managing enterprise projects, see the Enterprise Management User Guide.

Select specifications for the dedicated load balancer based on Table 2.

**Table 2** Load balancer specifications
Parameter	Description
Specifications	Select Elastic or Fixed if pay-per-use is chosen as the billing mode. Specification type 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. Load balancing type Application load balancing (HTTP/HTTPS): supports HTTP and HTTPS. This option is a great fit for workloads that require high performance at Layer 7, such as real-time audio and video, interactive livestreaming, and game applications. Networking load balancing (TCP/UDP/TLS): supports TCP, UDP, and TLS. This option is a great fit for heavy-traffic and high-concurrency workloads at Layer 4, such as file transfer, instant messaging, and online video applications. Select either Application load balancing (HTTP/HTTPS) or Network load balancing (TCP/UDP/TLS) 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/TLS), respectively. Select the desired specifications based on your service size by referring to Specifications of Dedicated Load Balancers.

Complete the network configurations based on Table 3.

**Table 3** Configuring network parameters
Parameter	Description
Network Type	Specifies the network where the load balancer works. You can select one or more network types. Private IPv4 network: The load balancer routes IPv4 requests from the clients to backend servers in a VPC. If you want the load balancer to route requests from the Internet, bind an EIP to the load balancer. 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 option, no IP address will be assigned to the load balancer. If this happens, 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 works. 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. You can create a load balancer in a VPC subnet shared by another account for improved resource management and reduced O&M costs. For more information about VPC sharing, see VPC Sharing in the Virtual Private Cloud User Guide.
Frontend Subnet	Specifies the frontend subnet from which an IP address will be assigned to the dedicated 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. IP addresses in this subnet will be assigned to load balancers for receiving requests based on the configured network type. Private IPv4 network: IPv4 private addresses will be assigned. IPv6 network: IPv6 private or public addresses will be assigned. NOTE: If you select IPv6 network for Network Type and the selected VPC does not have any subnet that supports IPv6, enable IPv6 for at least one subnet or create a subnet that supports IPv6. For details, see the Virtual Private Cloud User Guide.
IPv4 Address	Specifies how you want the IPv4 address to be assigned if Network Type is set to Private IPv4 network. Automatically assign IP address: The system 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?
Backend Subnet	Specifies the backend subnet from which an IP address will be assigned to the dedicated 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. Click Create Subnet on the right to 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 by a load balancer to communicate with the backend servers depends on how many AZs you have selected, how you configure the specifications, and whether you enable the IP as a backend option. See how many IP addresses are actually required 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.
IPv6 Address	Specifies how you want the IPv6 address to be assigned if Network Type is set to IPv6 network. Assign automatically: The system automatically assigns an IPv6 address to the load balancer. Manually specify: You need to manually specify an IPv6 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?
Shared Bandwidth	Specifies the shared bandwidth that the IPv6 address will be added to. A shared bandwidth allows multiple EIPs in the same region to share the same bandwidth. You can choose not to select a shared bandwidth, select an existing shared bandwidth, or buy a shared bandwidth.
IP as a Backend	Specifies whether to associate backend servers that are not in the VPC of the load balancer. After this option 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 need to 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.

Configure an EIP for the load balancer to enable it to route IPv4 requests over the Internet based on Table 4.

**Table 4** Selecting an EIP for the load balancer
Parameter	Description
EIP	Specifies the public IP address that will be bound to the load balancer for receiving and forwarding requests over the Internet. Auto assign: A new EIP will be assigned to the load balancer. Use existing: Select an existing EIP. Not required: You can bind an EIP to the load balancer later. NOTE: If you want to enable a load balancer to communicate with the Internet through a global EIP, you can bind a global EIP to the load balancer.
EIP Type	Specifies the link type (BGP) when a new EIP is used. Dynamic BGP: If there are changes on a network using dynamic BGP, routing protocols provide automatic, real-time optimization of network configurations, ensuring network stability and optimal user experience. This option works well for workloads that require higher network stability and connectivity, such as financial transactions, online games, large-scale enterprise applications, and livestreaming services. Static BGP: If there are changes on a network using static BGP, carriers cannot adjust network configurations in real time to ensure optimal user experience. This is a more cost-effective option for workloads that are running in relatively stable networks and have disaster recovery setups. For details see What Are the Differences Between Static BGP and Dynamic BGP?
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: Load balancers that have EIPs bound in the same region can share the selected bandwidth, helping you reduce public network bandwidth costs.
Bandwidth (Mbit/s)	Specifies the maximum bandwidth.

Configure other parameters for the load balancer as described in Table 5.

**Table 5** Configuring other parameters
Parameter	Description
Advanced Settings (Optional) > Description	Click to expand the configuration area and set this parameter. Enter a description about the load balancer in the text box as required. Enter up to 255 characters. Angle brackets (<>) are not allowed.
Advanced Settings (Optional) > Tag	Click to expand the configuration area and set this parameter. Add tags to the load balancer 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 6. You can add a maximum of 20 tags.

**Table 6** Tag key and value requirements
Parameter	Requirement
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 (@).
Tag value	Can contain a maximum of 43 characters. Can contain only letters, digits, underscores (_), hyphens (-), at signs (@).

Click Next.

Exporting the Load Balancer List

You can export the information about all load balancers under your account to a local directory as an Excel file.

This file records the name, ID, status, type, and specifications of the load balancers.

Log in to the management console.
In the upper left corner of the page, click and select the desired region and project.
Click in the upper left corner to display Service List and choose Networking > Elastic Load Balance.
In the upper left corner of the load balancer list, click Export.
The system will export information about all of your load balancers as an Excel file to a local directory.