Help Center> Elastic Load Balance> User Guide> Load Balancer> Creating a Shared Load Balancer
Updated on 2024-05-07 GMT+08:00

Creating a Shared Load Balancer


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

Load balancers receive requests from clients and route them to backend servers, which answer to these requests over the private network.


  • 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 and associate a backend server 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. Hover on in the upper left corner to display Service List and choose Networking > Elastic Load Balance.
  4. On the Load Balancers page, click Buy Elastic Load Balancer. Configure the parameters based on Table 1.
    Table 1 Parameters for configuring the basic information



    Example Value


    Specifies the type of the load balancer. The type cannot be changed after the load balancer is created.

    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.



    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.



    Specifies the load balancer name.


    Enterprise Project

    Specifies an enterprise project by which cloud resources and members are centrally managed.



    Provides supplementary information about the load balancer.



    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 specifications, see Table 2.

    A maximum of 10 tags can be added.


    If your organization has configured tag policies for ELB, add tags to load balancers based on the tag policies. If you add a tag that does not comply with the tag policies, load balancers may fail to be created. Contact your organization administrator to learn more about tag policies.

    • Key: elb_key1
    • Value: elb-01
    Table 2 Tag naming rules



    Example Value

    Tag key

    • Cannot be empty.
    • Must be unique for the same load balancer.
    • Can contain a maximum of 36 characters.
    • Only letters, digits, underscores (_), hyphens (-), at signs (@), and Chinese characters are allowed.


    Tag value

    • Can contain a maximum of 43 characters.
    • Only letters, digits, underscores (_), hyphens (-), at signs (@), and Chinese characters are allowed.


  5. Configure the network parameters based on Table 3.
    Table 3 Parameters for network configurations



    Example Value

    Network Type

    Specifies the network type of a load balancer. You can select either of the following:

    • Public network: The load balancer routes requests from the clients to backend servers over the Internet.
    • Private network: A private network load balancer routes requests from the clients to backend servers in the same VPC.

    Public IPv4 network


    Specifies the VPC where the load balancer will work.

    Select an existing VPC or create a new one.

    For more information about VPC, see the Virtual Private Cloud User Guide.


    Frontend Subnet

    Specifies the subnet where the load balancer will work. Shared load balancers support private IPv4 network by default.

    The system assigns IPv4 private addresses in this subnet to load balancers.


    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.

    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 a load balancer, configure access control for all listeners added to the load balancer.

    For details, see Access Control.

    Automatically assign IP address

    Guaranteed Performance

    Specifies whether to enable the guaranteed performance option. This function allows your load balancers to handle up to 50,000 concurrent connections, 5,000 new connections per second, and 5,000 queries per second.



    Specifies the public IP address that will be bound to the load balancer for receiving and forwarding requests over the Internet.

    You can use an existing EIP or apply for a new one.

    The following options are available:

    • New EIP: The system will automatically assign an EIP.
    • Use existing: Select an existing EIP.

    New EIP

    EIP Type

    Specifies the link type (BGP) when a new EIP is used.

    • Static BGP: When changes occur on a network using static BGP, carriers cannot adjust network configurations in real time to ensure optimal user experience.
    • 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 total traffic you use.



    Specifies the maximum bandwidth when a new EIP is used, in Mbit/s.

    10 Mbit/s

  6. Click Next.
  7. Confirm the configuration and submit your request.