Creating a Dedicated Load Balancer

Scenario

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

   Parameter	Description	Example Value
   Type	Specifies the type of the load balancer.	Dedicated
   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. NOTE: If requests are from the Internet, the load balancer in each AZ you select routes the requests based on source IP addresses. If you deploy a load balancer in two AZs, the requests the load balancers can handle will be doubled. For requests from a private network: If clients are in the AZ you selected when you created the load balancer, requests are distributed by the load balancer in this AZ. If the load balancer is unavailable, requests are distributed by the load balancer in another AZ you select. If the load balancer is available but the connections that the load balancer needs to handle exceed the amount defined in the specifications, service may be interrupted. To address this issue, you need upgrade specifications. You can monitor traffic usage on private network by AZ. If clients are in an AZ that is not selected when you create the load balancer, requests are distributed by the load balancer in each AZ you select based on source IP addresses. If clients are in a VPC that is different from where the load balancer works, the load balancer in the AZ where the original VPC subnet resides routes the requests. If the load balancer in this AZ is unavailable, requests are distributed by the load balancer in another AZ.	-
   Specifications	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 plan by referring to Specifications of Dedicated Load Balancers. For application load balancing, the number of IP addresses varies depending on the specification. You can view the number of IP addresses required by the load balancer in the advanced settings. The performance of load balancers varies depending on the selected specifications. You can evaluate the actual traffic and select appropriate specifications based on the key metrics.	Medium II

5. Configure the parameters based on Table 2.

   Table 2 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 the IP as a backend 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.	N/A
   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 is 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 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. You need to configure this parameter regardless of the selected network type. 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
   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 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
   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-assigned 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.	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. Dedicated: You specify the maximum bandwidth and pay for the total traffic you use. Shared Bandwidth	Shared Bandwidth
   Bandwidth	Specifies the maximum bandwidth.	100 Mbit/s

6. Configure other parameters about the load balancer as described in Table 3.

   Table 3 Other parameters

   Parameter	Description	Example Value
   Name	Specifies the load balancer name.	elb-test
   Enterprise Project	Selects an enterprise project by which cloud resources and members are centrally managed.	default
   Advanced settings
   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 on the console.	Subnet of the load balancer
   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 4. A maximum of 10 tags can be added.	Key: elb_key1 Value: elb-01

   Table 4 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, hyphens (-), underscores (_), and Unicode characters from \u4e00 to \u9fff are allowed.	elb_key1
   Value	Can contain a maximum of 43 characters. Only letters, digits, periods (.), hyphens (-), underscores (_), and Unicode characters from \u4e00 to \u9fff are allowed.	elb-01

7. Click Create Now.
8. Confirm the configuration and submit your request.