Creating a Shared Load Balancer

Scenarios

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

Notes and Constraints

• After a load balancer is created, the 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 shared load balancer, you need to add a listener to it.

Procedure

1. Go to the Buy Elastic Load Balancer page.
2. 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 shared load balancer. The type cannot be changed after the load balancer is created. Shared load balancers are suitable for workloads with low traffic, such as small websites and common HA applications. For details about the differences, see Differences Between Dedicated and Shared Load Balancers.
   Billing Mode	Specifies the billing mode of the shared load balancer. You are charged for how long you use each load balancer.
   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. For details about creating and managing enterprise projects, see the Enterprise Management User Guide.

3. Configure the network parameters based on Table 2.

   Table 2 Configuring network parameters

   Parameter	Description
   Network Type	Private IPv4 network is selected by default. The load balancer routes IPv4 requests from 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.
   VPC	Specifies the VPC where the shared 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. 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 shared load balancer to receive client requests. IP addresses in this subnet will be assigned to your load balancers.
   IPv4 Address	Specifies how you want the IPv4 address to be assigned. 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 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?
   Guaranteed Performance	Specifies whether to enable the guaranteed performance option. This option allows your load balancers to handle up to 50,000 concurrent connections, 5,000 new connections per second, and 5,000 queries per second. This option is enabled by default and cannot be disabled.

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

   Table 3 Selecting an EIP for the load balancer

   Parameter	Description
   Elastic IPs	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: EIPs are not required.
   Bandwidth 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. 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 that is a great fit 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.

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

   Table 4 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 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 5. You can add a maximum of 20 tags.

   Table 5 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 (@).
   Tag value	Can contain a maximum of 43 characters. Can contain only letters, digits, underscores (_), hyphens (-), at signs (@) are allowed.

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

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 Networking > Elastic Load Balance.
4. 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.