Creating a Dedicated Load Balancer

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

• 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.

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
   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.
   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.

   Table 2 Load balancer specifications

   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.
   Load Balancing Type	Application: supports HTTP, QUIC, 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. Network: supports TCP, TLS, and UDP. This option works well for heavy-traffic and high-concurrency workloads at Layer 4, such as file transfer, instant messaging, and online video applications. Network + Application: Both network (TCP/UDP/TLS) and application (HTTP/HTTPS) load balancers can be created, meeting multi-dimensional traffic distribution requirements.
   AZ	Specifies the AZs where the 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.
   Specification Type	Select Elastic or Fixed if pay-per-use is chosen as the billing mode. Elastic: This type works well for fluctuating traffic, and you will be billed for how many LCUs you use. Fixed: This type is suitable for stable traffic, and you will be billed for the LCUs that are calculated based on each fixed specification you select.

   Table 3 Tag naming rules

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

5. Configure the network parameters based on Table 4.

   Table 4 Parameters for network configurations

   Parameter	Description
   Network Type	Specifies the network where the load balancer works. You can select one or more network types. If you do not select any option, no IP address will be assigned to the load balancer and the load balancer cannot communicate with the clients after it is created. If you need to use ELB or test network connectivity, ensure that the load balancer has a public or private IP address bound. Private IPv4 network: A private IPv4 address will be assigned to the load balancer to route 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.
   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 another frontend subnet to the load balancer. IP addresses in a frontend subnet will be assigned to load balancers for receiving requests based on the configured network type. Private IPv4 network: An IPv4 private address in the IPv4 subnet will be assigned to the load balancer. IPv6 network: An IPv6 address in the IPv6 subnet will be assigned to the load balancer. NOTE: If you select IPv6 network for Network Type and the selected VPC does not have any subnet that supports IPv6, enable IPv6 for a subnet or create a subnet that supports IPv6 in the VPC. 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. Configure access control for listeners 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 IP addresses will be assigned to the load balancer to forward requests to backend servers. Subnet of the load balancer is selected by default. You can select a subnet in the VPC where the load balancer works. You can also create a subnet. NOTE: If IPv6 is not enabled for the backend subnet you select when creating 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. You can check the number of IP addresses actually used by the load balancer on the console. An application load balancer requires 8 to 30 additional IP addresses in the backend subnet for forwarding traffic. 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. 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 there are network ACL rules configured, the clients can still 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?.
   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.
   Configuring an EIP for the load balancer
   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 Public IPv4 network. 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.
   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.

After a load balancer is created, you can export the information about all load balancers in your account to a local directory as an Excel file.

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

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.