Creating a Shared Load Balancer
Scenarios
You have prepared everything required for creating a shared load balancer. For details, see Shared Load Balancer Overview.
Shared load balancers receive requests from clients and route them 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 a shared load balancer and select a different VPC.
- To ping the IP address of a shared load balancer, you need to add a listener and associate a backend server to it.
Procedure
- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Click in the upper left corner to display Service List and choose Networking > Elastic Load Balance.
- 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
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.
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 quicker resource access, select the nearest region.
Name
Specifies the name of the shared load balancer.
Enterprise Project
Specifies an enterprise project by which cloud resources and members are centrally managed.
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 rules, see Table 2.
A maximum of 20 tags can be added.
Table 2 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.
- 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.
- Configure the network parameters based on Table 3.
Table 3 Parameters for network configurations Parameter
Description
Network Type
Specifies the network type of a load balancer.
- Public IPv4 network: The load balancer routes IPv4 requests from the clients to backend servers over the Internet.
- Private IPv4 network: The load balancer routes IPv4 requests from the clients to backend servers in the same VPC as the load balancer.
VPC
Specifies the VPC where the shared load balancer will work. You cannot change the VPC after the load balancer is created. Plan the VPC as required.
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: You need to 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 What Is Access Control?
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.
This function is enabled by default and cannot be disabled.
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 assign a new one.
The following options are available:
- New EIP: The system will automatically assign an EIP.
- Use existing: Select an existing 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.
Billed By
Specifies how the bandwidth will be billed.
- 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: Only the shared bandwidth will be billed. There will be no additional bandwidth or traffic costs for EIPs added to the shared bandwidth.
Bandwidth
Specifies the maximum bandwidth when a new EIP is used, in Mbit/s.
- Click Next.
- Confirm the configuration and submit your request.
Exporting the Load Balancer List
After a load balancer is created, you can export the information about all load balancers under your account to a local directory as an Excel file.
- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Click in the upper left corner to display Service List and choose Networking > Elastic Load Balance.
- In the upper left corner of the load balancer list, click Export.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot