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

Creating a Dedicated Load Balancer

Scenarios

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

Constraints

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

Procedure

  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. Complete the basic configurations based on Table 1.
    Table 1 Parameters for configuring the basic information

    Parameter

    Description

    Example Value

    Type

    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.

    Dedicated

    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

    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 of the load balancer. You can deploy a load balancer in multiple AZs for high availability. If an AZ becomes faulty or unavailable, the load balancers in other AZs can route requests to backend servers to ensure service continuity and improve application reliability.

    If you deploy a load balancer in multiple AZs, its performance such as the number of new connections and the number of concurrent connections will multiply. For example, if you deploy a dedicated load balancer in two AZs, it can handle up to 40 million concurrent connections.

    For details about AZ planning, see AZ.

    -

    Specifications

    Select Elastic or Fixed if pay-per-use is chosen as the billing mode.

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

    Select either Application load balancing (HTTP/HTTPS) or Network load balancing (TCP/UDP) 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), respectively. Select the desired specifications based on your service size by referring to Specifications of Dedicated Load Balancers.

    NOTE:

    For details about the regions where elastic specification is available, see Function Overview.

    Medium II

    Name

    Specifies the load balancer name.

    elb-test

    Enterprise Project

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

    NOTE:

    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

    Item

    Requirement

    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.

    elb_key1

    Tag value

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

    elb-01

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

    Parameter

    Description

    Example Value

    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, configure correct VPC routes to ensure requests can be routed to backend servers.
    • If you enable this function, more IP addresses in the subnet will be occupied. 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.

    -

    Network Type

    Specifies the network where the load balancer works. You can select one or more network types.

    • Public IPv4 network: The load balancer routes requests from the clients to backend servers over the Internet.
    • Private IPv4 network: The load balancer routes requests from the clients to backend servers in a VPC.
    • 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 of the options, 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.

    Public IPv4 network

    VPC

    Specifies the VPC where the load balancer works.

    Select an existing VPC or create a new one.

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

    vpc-test

    Frontend Subnet

    Specifies the subnet where the load balancer will work.

    The system assigns IP addresses to load balancers for receiving requests based on the configured network type.

    • IPv4 private network: assigns IPv4 private addresses.
    • IPv6 network: assigns IPv6 private or public addresses.
    NOTE:

    If you select IPv6 network for Network Type and the selected VPC does not have any subnet that supports IPv6, enable IPv6 for the subnets or create a subnet that supports IPv6. For details, see the Virtual Private Cloud User Guide.

    subnet-test

    Backend Subnet

    The load balancer uses the IP addresses in the backend subnet to forward requests to the backend servers.

    • Select Subnet of the load balancer by default.
    • Select an existing subnet in the VPC where the load balancer works.
    • Add a new subnet
    NOTE:
    • The number of IP addresses required depend on the specifications, number of AZs, and IP as a backend function you have configured when you create the load balancer. The actual number of occupied IP addresses depends on that displayed 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.

    Subnet of the load balancer

    Private IPv4 network configuration

    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:

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

    For details, see Access Control.

    Automatically assign IP address

    IPv6 network configuration

    IPv6 Address

    Specifies how you want the IPv6 address to be assigned.

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

    Automatically assign IP address

    Shared Bandwidth

    Specifies the shared bandwidth that the IPv6 address will be added to.

    You can choose not to select a shared bandwidth, select an existing shared bandwidth, or assign a shared bandwidth.

    Skip

    Public IPv4 network configuration

    EIP

    This parameter is mandatory when Network Type is set to IPv4 public network.

    • New EIP: The system will assign a new EIP to the load balancer.
    • Use existing: Select an existing IP address.

    -

    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 outbound traffic you use.
    • Shared Bandwidth

    Shared Bandwidth

    Bandwidth

    Specifies the maximum bandwidth.

    100 Mbit/s

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

Popular Questions

  • Can ELB Work in a Different AZ from Backend Servers?

    Yes. ELB can route requests to backend servers in an AZ that is different from where the load balancer is deployed. To reduce network latency and improve access speed, you are suggested to deploy your load balancer in the AZ where backend servers are running.

  • Can I Change the Specifications of an Existing Load Balancer?

    Yes. For details, see Changing the Specifications of a Dedicated Load Balancer.