Creating a Shared Load Balancer

Scenarios

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 the requests to backend servers, which answer to these requests over the private network.

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 the VPC during creation.

  • If a load balancer status is unhealthy, submit a service ticket to seek technical support.

  • To ping the IP address of a load balancer, you need to add a listener and associate a backend server to it.

Procedure

  1. Log in to the management console.

  2. In the upper left corner of the page, click image1 and select the desired region and project.

  3. Click image2 in the upper left corner to display Service List and choose Network > Elastic Load Balancing.

  4. On the Load Balancers page, click Create Elastic Load Balancer. Configure the parameters based on Table 1.

    Table 1 Parameters for configuring the basic information

    Parameter

    Description

    Example Value

    Type

    Specifies the type of the load balancer.

    Shared

    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.

    elb-test

    Enterprise Project

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

    default

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

    A maximum of 10 tags can be added.

    • Key: elb_key1

    • Value: elb-01

    Table 2 Tag naming rules

    Parameter

    Requirement

    Example Value

    Tag key

    • Cannot be empty.

    • Must be unique for the same load balancer.

    • Can contain a maximum of 36 characters.

    • Can contain only the following character types:

      • Uppercase letters

      • Lowercase letters

      • Digits

      • Special characters, including hyphens (-), underscores (_), and at signs (@)

    elb_key1

    Tag value

    • Can contain a maximum of 43 characters.

    • Can contain only the following character types:

      • Uppercase letters

      • Lowercase letters

      • Digits

      • Special characters, including hyphens (-), underscores (_), and at signs (@)

    elb-01

  5. Configure the network parameters based on Table 3.

    Table 3 Parameters for network configurations

    Parameter

    Description

    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: The load balancer routes requests from the clients to backend servers in the same VPC.

    Public IPv4 network

    VPC

    Specifies the VPC where the load balancer works.

    Select an existing VPC or create 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.

    Note

    Firewall rules configured for the backend subnet of the load balancer will not restrict the traffic from the clients to the load balancer. If firewall 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 Access Control.

    Automatically assign IP address

    Public IPv4 network configuration

    EIP

    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.

    • New EIP: The system will automatically assign an EIP.

    • Use existing: Select an existing EIP.

      5_bgp EIPs are recommended.

    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 the bandwidth type of the EIP.

    Dedicated: You specify the maximum bandwidth. The bandwidth is suitable for fluctuating traffic.

    Dedicated

    Bandwidth

    Specifies the maximum bandwidth when a new EIP is used, in Mbit/s. The value ranges from 1 Mbit/s to 1000 Mbit/s.

    10 Mbit/s

  6. Click Create Now.

  7. Confirm the configuration and submit your request.

last updated: 2024-11-13 14:50 UTC - commit: dc0473f339644f421ca4d648c4746583f80203ae