- What's New
- Function Overview
-
Service Overview
- ELB Infographics
- What Is ELB?
- ELB Advantages
- How ELB Works
- Application Scenarios
- Differences Between Dedicated and Shared Load Balancers
- Load Balancing on a Public or Private Network
- Network Traffic Paths
- Specifications of Dedicated Load Balancers
- Notes and Constraints
- Security
- Permissions
- Product Concepts
- ELB and Other Services
-
Billing
- Billing Overview
- Billing Mode
- Billing Items (Dedicated Load Balancers)
- Billing Items (Shared Load Balancers)
- Billing Examples
- Bills
- Arrears
- Stopping Billing
- Cost Management
-
FAQs
- When Do I Need Public Bandwidth for ELB?
- Will I Be Billed for Both the Bandwidth Used by the Load Balancer and the Bandwidth Used by Backend Servers?
- Do I Need to Adjust the Bandwidth of Shared Load Balancers Based on the Bandwidth Used by Backend Servers?
- Can I Modify the Bandwidth of a Load Balancer?
- What Functions Will Become Unavailable If a Load Balancer Is Frozen?
- Getting Started
-
User Guide
-
User Guide for Dedicated Load Balancers
- Using a Dedicated Load Balancer
- Permissions Management
-
Load Balancer
- Dedicated Load Balancer Overview
- Creating a Dedicated Load Balancer
- Enabling or Disabling Modification Protection for Dedicated Load Balancers
- Modifying the Basic Configurations of a Dedicated Load Balancer
- Modifying the Network Configurations of a Dedicated Load Balancer
- Exporting Dedicated Load Balancers
- Deleting a Dedicated Load Balancer
- Copying a Dedicated Load Balancer
- Enabling or Disabling a Load Balancer
- Listener
- Backend Server Group
- Backend Server
- Health Check
- Security
- Access Logging
- Tags and Quotas
- Cloud Eye Monitoring
- Auditing
-
User Guide for Shared Load Balancers
- Permissions Management
-
Load Balancer
- Shared Load Balancer Overview
- Creating a Shared Load Balancer
- Configuring Modification Protection for Shared Load Balancers
- Changing the Network Configurations of a Shared Load Balancer
- Deleting a Shared Load Balancer
- Enabling or Disabling a Shared Load Balancer
- Enabling Guaranteed Performance for a Shared Load Balancer
- Listener
- Backend Server Group
- Backend Server
- Health Check
- Security
- Access Logging
- Tags and Quotas
- Cloud Eye Monitoring
- Auditing
- Self-service Troubleshooting
- Appendix
-
User Guide for Dedicated Load Balancers
-
Best Practices
- Using IP as a Backend to Route Traffic Across Backend Servers
- Using Advanced Forwarding for Application Iteration
- Integrating WAF with ELB to Protect Your Websites
- Configuring HTTPS Mutual Authentication to Improve Service Security
- Using ELB to Redirect HTTP Requests to an HTTPS Listener for Higher Service Security
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs (V3)
- API Version
- Quota
- AZ
- Load Balancer Flavor
- Reserved IP Address
-
Load Balancer
- Creating a Load Balancer
- Querying Load Balancers
- Viewing Details of a Load Balancer
- Updating a Load Balancer
- Deleting a Load Balancer
- Deleting a Load Balancer and Its Associated Resources
- Querying the Status Tree of a Load Balancer
- Deploying a Load Balancer in Other AZs
- Removing a Load Balancer from AZs
- Certificate
- Security Policy
- IP Address Group
- Listener
- Backend Server Group
- Backend Server
- Health Check
- Forwarding Policy
- Forwarding Rule
- Active/Standby Backend Server Group
- Log
- API (V2)
-
API (OpenStack API)
-
Tag
- Adding a Tag to a Load Balancer
- Batch Adding Load Balancer Tags
- Batch Deleting Load Balancer Tags
- Querying All Tags of a Load Balancer
- Querying the Tags of All Load Balancers
- Querying Load Balancers by Tag
- Deleting a Tag from a Load Balancer
- Adding a Tag to a Listener
- Batch Adding Tags to a Listener
- Batch Deleting Tags from a Listener
- Querying All Tags of a Listener
- Querying the Tags of All Listeners
- Querying Listeners by Tag
- Deleting a Tag from a Listener
- Status Codes
-
Tag
- Examples
- Permissions and Supported Actions
- Appendix
-
Historical APIs
- Shared Load Balancer APIs (OpenStack)
- Asynchronous Job Query
- Querying Versions
-
Getting Started
- Creating a Load Balancer
- Obtaining a Token
- Creating a Load Balancer
- Creating a Public Network Load Balancer
- Adding a Listener
- Creating a Backend Server Group
- Adding Backend Servers
- Configuring a Health Check
- Adding a Forwarding Policy
- Adding a Forwarding Rule
- Adding a Whitelist
- Creating an SSL Certificate
- Cascade Delete
- SDK Reference
-
FAQs
- Popular Questions
-
Service Abnormality
- Why Can't I Access My Backend Servers Through a Load Balancer?
- Why Does a Server Occasionally Time Out When a Client Access It Through Different Load Balancers or Different Listeners of a Load Balancer?
- What Can I Do If ELB Can't Be Accessed or Traffic Routing is Interrupted?
- How Can I Handle Abnormal Status Codes?
- How Do I Handle Abnormal Request Headers?
- How Do I Check for Traffic Inconsistencies?
- Why Does ELB Fail to Distribute Traffic Evenly?
- How Do I Check If There Is Excessive Access Delay?
- What Do I Do If a Load Balancer Fails a Stress Test?
- How Do I Check If Sticky Sessions Failed to Take Effect?
-
ELB Functionality
- Can Load Balancers Be Used Separately?
- Can ELB Block DDoS Attacks and Secure Web Code?
- What Types of APIs Does ELB Provide? What Are Permissions of ELB?
- Can Backend Servers of a Load Balancer Run Different OSs?
- Can ELB Be Used Across Accounts or VPCs?
- Can a Backend Server Access Its Load Balancer?
- Can Both the Listener and Backend Server Group Use HTTPS?
- Does ELB Support IPv6 Networks?
- How Do I Determine the Server Response Time Based on Monitoring Data and Logs?
- How Can I Transfer the IP Address of a Client?
- What Are the Differences Between Persistent Connections and Sticky Sessions?
- How Do I Test Sticky Sessions Using Linux Curl Commands?
-
Load Balancers
- What Is Quota?
- How Does ELB Distribute Traffic?
- How Can I Configure Load Balancing for Containerized Applications?
- Can I Bind Multiple EIPs to a Load Balancer?
- Why Multiple IP Addresses Are Required When I Create a Dedicated Load Balancer?
- Can Backend Servers Access the Internet Using the EIP of the Load Balancer?
- Do Shared Load Balancers Have Specifications?
- What Is the Difference Between the Bandwidth Defined in Each Specification of a Dedicated Load Balancer and the Bandwidth of an EIP?
- How Do I Combine ELB and WAF?
-
Listeners
- What Are the Relationships Between Load Balancing Algorithms and Sticky Session Types?
- Will ELB Stop Distributing Traffic Immediately After a Listener Is Deleted?
- Does ELB Have Restrictions on the File Upload Speed and Size?
- Can Multiple Load Balancers Route Requests to One Backend Server?
- How Is WebSocket Used?
- What Are the Three Timeouts of a Listener and What Are the Default Durations?
- Why Can't I Select the Target Backend Server Group When Adding or Modifying a Listener?
- Why Is There a Security Warning After a Certificate Is Configured for an HTTPS Listener?
- Why Is a Forwarding Policy in the Faulty State?
-
Backend Servers
- Can Backend Servers Access the Internet After They Are Associated with a Load Balancer?
- Can ELB Distribute Traffic Across Servers That Are Not Provided by Huawei Cloud?
- Why Are Backend Servers Frequently Accessed by IP Addresses in 100.125.0.0/16 or 214.0.0.0/8?
- Can ELB Route Traffic Across Regions?
- Does Each Backend Server Need an EIP to Receive Requests from a Public Network Load Balancer?
- How Do I Check the Network Conditions of a Backend Server?
- How Can I Check the Network Configuration of a Backend Server?
- How Do I Check the Status of a Backend Server?
- How Do I Check Whether a Backend Server Can Be Accessed Through an EIP?
- Why Is the Number of Active Connections Monitored by Cloud Eye Different from the Number of Connections Established with the Backend Servers?
- Why Can I Access Backend Servers After a Whitelist Is Configured?
- When Will the Changes to Server Weights Be Applied?
-
Health Checks
- How Do I Troubleshoot an Unhealthy Backend Server of a Dedicated Load Balancer?
- How Do I Troubleshoot an Unhealthy Backend Server of a Shared Load Balancer?
- Why Is the Interval at Which Backend Servers Receive Health Check Packets Different from the Configured Interval?
- How Does ELB Perform UDP Health Checks? What Are the Precautions for UDP Health Checks?
- Why Does ELB Frequently Send Requests to Backend Servers During Health Checks?
- When Does a Health Check Start?
- What Do I Do If a Lot of Access Logs Are Generated During Health Checks?
- What Status Codes Will Be Returned If Backend Servers Are Identified as Healthy?
- Certificates
- Access Logging
- Monitoring
-
Billing
- When Do I Need Public Bandwidth for ELB?
- Will I Be Billed for Both the Bandwidth Used by the Load Balancer and the Bandwidth Used by Backend Servers?
- Do I Need to Adjust the Bandwidth of Shared Load Balancers Based on the Bandwidth Used by Backend Servers?
- Can I Modify the Bandwidth of a Load Balancer?
- What Functions Will Become Unavailable If a Load Balancer Is Frozen?
- Videos
- Glossary
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Load Balancer
- Listener
- Backend Server
- Health Check
- Certificate
- Access Logging
- Monitoring
- Auditing
-
FAQs
- Questions Summary
- ELB Usage
- Load Balancer
- Listener
-
Backend Server
- Why Is the Interval at Which Backend Servers Receive Health Check Packets Is Different from the Configured Health Check Interval?
- Can Backend Servers Access the Public Network After They Are Associated with a Load Balancer?
- How Can I Check the Network Conditions of a Backend Server?
- How Can I Check the Network Configuration of a Backend Server?
- How Can I Check the Status of a Backend Server?
- When Is a Backend Server Considered Healthy?
- Health Check
- Obtaining Source IP Addresses
- HTTP/HTTPS Listeners
- Sticky Session
- Appendix
- Change History
-
API Reference (ME-Abu Dhabi Region)
- Before You Start
- API Overview
- Calling APIs
- Getting Started
- Load Balancer APIs
- Load Balancer (Enterprise Project) APIs
- Common Parameters
- Appendix
- Change History
-
User Guide (Paris Region)
-
Service Overview
- What Is ELB?
- Product Advantages
- How ELB Works
- Application Scenarios
- Differences Between Dedicated and Shared Load Balancers
- Load Balancing on a Public or Private Network
- Network Traffic Paths
- Specifications of Dedicated Load Balancers
- Quotas and Constraints
- Billing (Shared Load Balancers)
- Billing (Dedicated Load Balancers)
- Permissions
- Product Concepts
- How ELB Works with Other Services
- Getting Started
-
Load Balancer
- Overview
- Preparations for Creating a Load Balancer
- Creating a Dedicated Load Balancer
- Creating a Shared Load Balancer
- Configuring Deletion Protection for Load Balancers
- Modifying the Bandwidth
- Changing the Specifications of a Dedicated Load Balancer
- Changing an IP Address
- Binding an IP Address to or Unbinding an IP Address from a Load Balancer
- Adding to or Removing from an IPv6 Shared Bandwidth
- Exporting the Load Balancer List
- Deleting a Load Balancer
- Listener
- Advanced Features of HTTP/HTTPS Listeners
- Backend Server Group
- Backend Server (Dedicated Load Balancers)
- Backend Server (Shared Load Balancers)
- Certificate
- Access Control
- TLS Security Policy
- Tag
- Access Logging
- Monitoring
- Auditing
- Load Balancer Migration
- Permissions Management
- Quotas
-
FAQ
- Popular Questions
- Why Can't I Access My Backend Servers Through a Load Balancer?
- What Can I Do If ELB Can't Be Accessed or Traffic Routing is Interrupted?
- How Can I Handle Error Codes?
- Can ELB Be Used Separately?
- Does ELB Support Persistent Connections?
- Does ELB Support FTP on Backend Servers?
- Is an EIP Assigned Exclusively to a Load Balancer?
- How Many Load Balancers and Listeners Can I Have?
- What Types of APIs Does ELB Provide? What Are Permissions of ELB?
- Can I Adjust the Number of Backend Servers When a Load Balancer is Running?
- Can Backend Servers Run Different OSs?
- Can I Configure Different Backend Ports for a Load Balancer?
- Can ELB Be Used Across Accounts or VPCs?
- Can Backend Servers Access the Ports of a Load Balancer?
- Can Both the Listener and Backend Server Group Use HTTPS?
- Can I Change the VPC and Subnet for My Load Balancer?
- Can I Upgrade a Shared Load Balancer to a Dedicated Load Balancer Without Interrupting Traffic Routing?
- Does ELB Support IPv6 Networks?
- How Do I Check for Traffic Inconsistencies?
- How Do I Check If Traffic Is Being Evenly Distributed?
- How Do I Check If There Is Excessive Access Delay?
- What Do I Do If a Load Balancer Fails a Stress Test?
-
Load Balancers
- How Does ELB Distribute Traffic?
- How Can I Access a Load Balancer Across VPCs?
- How Can I Configure Load Balancing for Containerized Applications?
- Why Can't I Delete My Load Balancer?
- Do I Need to Configure EIP Bandwidth for My Load Balancers?
- Can I Bind Multiple EIPs to a Load Balancer?
- Why Multiple IP Addresses Are Required When I Create or Enable a Dedicated Load Balancer?
- Why Are Requests from the Same IP Address Routed to Different Backend Servers When the Load Balancing Algorithm Is Source IP Hash?
- Can Backend Servers Access the Internet Using the EIP of the Load Balancer?
- Do Shared Load Balancers Have Specifications?
- Will Traffic Routing Be Interrupted If the Load Balancing Algorithm Is Changed?
- What Is the Difference Between the Bandwidth Included in Each Specification of a Dedicated Load Balancer and the Bandwidth of an EIP?
- How Do I Combine ELB and WAF?
-
Listeners
- What Are the Relationships Between Load Balancing Algorithms and Sticky Session Types?
- Can I Bind Multiple Certificates to a Listener?
- What HTTP Headers Can I Configure for an HTTP and HTTP Listener?
- Will ELB Stop Distributing Traffic Immediately After a Listener Is Deleted?
- Does ELB Have Restrictions on the File Upload Speed and Size?
- Can Multiple Load Balancers Route Requests to One Backend Server?
- How Is WebSocket Used?
- Why Can't I Select the Target Backend Server Group When Adding or Modifying a Listener?
- Why Cannot I Add a Listener to a Dedicated Load Balancer?
-
Backend Servers
- Why Is the Interval at Which Backend Servers Receive Health Check Packets Different from What I Have Configured?
- Can Backend Servers Access the Internet After They Are Associated with a Load Balancer?
- Why Are Backend Servers Frequently Accessed by IP Addresses in 100.125.0.0/16?
- Can ELB Route Traffic Across Regions?
- Does Each Backend Server Need an EIP to Receive Requests from a Public Network Load Balancer?
- How Do I Check the Network Conditions of a Backend Server?
- How Can I Check the Network Configuration of a Backend Server?
- How Do I Check the Status of a Backend Server?
- When Is a Backend Server Considered Healthy?
- How Do I Check Whether a Backend Server Can Be Accessed Through an EIP?
- Why Is the Number of Active Connections Monitored by Cloud Eye Different from the Number of Connections Established with the Backend Servers?
- Why Can I Access Backend Servers After a Whitelist Is Configured?
- When Will Modified Weights Take Effect?
- Why Must the Subnet Where the Load Balancer Resides Have at Least 16 Available IP Addresses for Enabling IP as a Backend?
-
Health Checks
- How Do I Troubleshoot an Unhealthy Backend Server?
- Why Is the Interval at Which Backend Servers Receive Health Check Packets Different from the Configured Interval?
- How Does ELB Perform UDP Health Checks? What Are the Precautions for UDP Health Checks?
- Why Does ELB Frequently Send Requests to Backend Servers During Health Checks?
- When Does a Health Check Start?
- Do Maximum Retries Include Health Checks That Consider Backend Servers Unhealthy?
- What Do I Do If a Lot of Access Logs Are Generated During Health Checks?
- What Status Codes Will Be Returned If Backend Servers Are Identified as Healthy?
- Obtaining Source IP Addresses
-
HTTP/HTTPS Listeners
- Which Protocol Should I Select for the Backend Server Group When Adding an HTTPS Listener?
- Why Is There a Security Warning After a Certificate Is Configured?
- Why Is a Forwarding Policy in the Faulty State?
- Why Can't I Add a Forwarding Policy to a Listener?
- Why Cannot I Select an Existing Backend Server Group When Adding a Forwarding Policy?
- Sticky Sessions
- Certificates
- Monitoring
- Change History
-
Service Overview
-
API Reference (Paris Region)
- Before You Start
- API Overview
- Calling APIs
- Getting Started
- Dedicated Load Balancer APIs
- Classic Load Balancer APIs
- Enhanced Load Balancer APIs
- Appendix
- Change History
-
User Guide (Kuala Lumpur Region)
- Service Overview
- Getting Started
-
Load Balancer
- Overview
- Preparations for Creating a Load Balancer
- Creating a Dedicated Load Balancer
- Modifying the Bandwidth
- Changing the Specifications of a Dedicated Load Balancer
- Changing an IP Address
- Binding an IP Address to or Unbinding an IP Address from a Load Balancer
- Adding to or Removing from an IPv6 Shared Bandwidth
- Exporting the Load Balancer List
- Deleting a Load Balancer
- Listener
- Advanced Features of HTTP/HTTPS Listeners
- Backend Server Group
- Backend Server
- Certificate
- Access Control
- Access Logging
- Monitoring
- Auditing
- Quotas
-
FAQ
- Popular Questions
- Service Abnormality
-
ELB Functionality
- Can ELB Be Used Separately?
- Does ELB Support Persistent Connections?
- Does ELB Support FTP on Backend Servers?
- Is an EIP Assigned Exclusively to a Load Balancer?
- How Many Load Balancers and Listeners Can I Have?
- What Types of APIs Does ELB Provide? What Are Permissions of ELB?
- Can I Adjust the Number of Backend Servers When a Load Balancer is Running?
- Can Backend Servers Run Different OSs?
- Can I Configure Different Backend Ports for a Load Balancer?
- Can ELB Be Used Across Accounts or VPCs?
- Can Backend Servers Access the Ports of a Load Balancer?
- Can Both the Listener and Backend Server Group Use HTTPS?
- Can I Change the VPC and Subnet for My Load Balancer?
- Load Balancing Performance
-
Load Balancers
- How Does ELB Distribute Traffic?
- How Can I Access a Load Balancer Across VPCs?
- Do I Need to Configure EIP Bandwidth for My Load Balancers?
- Can I Bind Multiple EIPs to a Load Balancer?
- Why Multiple IP Addresses Are Required When I Create or Enable a Dedicated Load Balancer?
- Why Are Requests from the Same IP Address Routed to Different Backend Servers When the Load Balancing Algorithm Is Source IP Hash?
- Can Backend Servers Access the Internet Using the EIP of the Load Balancer?
- Will Traffic Routing Be Interrupted If the Load Balancing Algorithm Is Changed?
- What Is the Difference Between the Bandwidth Included in Each Specification of a Dedicated Load Balancer and the Bandwidth of an EIP?
-
Listeners
- What Are the Relationships Between Load Balancing Algorithms and Sticky Session Types?
- Can I Bind Multiple Certificates to a Listener?
- Will ELB Stop Distributing Traffic Immediately After a Listener Is Deleted?
- Does ELB Have Restrictions on the File Upload Speed and Size?
- Can Multiple Load Balancers Route Requests to One Backend Server?
- How Is WebSocket Used?
- Why Can't I Select the Target Backend Server Group When Adding or Modifying a Listener?
- Why Cannot I Add a Listener to a Dedicated Load Balancer?
-
Backend Servers
- Why Is the Interval at Which Backend Servers Receive Health Check Packets Different from What I Have Configured?
- Can Backend Servers Access the Internet After They Are Associated with a Load Balancer?
- Can ELB Route Traffic Across Regions?
- Does Each Backend Server Need an EIP to Receive Requests from a Public Network Load Balancer?
- How Do I Check the Network Conditions of a Backend Server?
- How Can I Check the Network Configuration of a Backend Server?
- How Do I Check the Status of a Backend Server?
- When Is a Backend Server Considered Healthy?
- Why Can I Access Backend Servers After a Whitelist Is Configured?
- When Will Modified Weights Take Effect?
- Why Must the Subnet Where the Load Balancer Resides Have at Least 16 Available IP Addresses for Enabling IP as a Backend?
-
Health Checks
- How Do I Troubleshoot an Unhealthy Backend Server?
- Why Is the Interval at Which Backend Servers Receive Health Check Packets Different from the Configured Interval?
- How Does ELB Perform UDP Health Checks? What Are the Precautions for UDP Health Checks?
- Why Does ELB Frequently Send Requests to Backend Servers During Health Checks?
- When Does a Health Check Start?
- Do Maximum Retries Include Health Checks That Consider Backend Servers Unhealthy?
- What Do I Do If a Lot of Access Logs Are Generated During Health Checks?
- What Status Codes Will Be Returned If Backend Servers Are Identified as Healthy?
- Obtaining Source IP Addresses
-
HTTP/HTTPS Listeners
- Which Protocol Should I Select for the Backend Server Group When Adding an HTTPS Listener?
- Why Is There a Security Warning After a Certificate Is Configured?
- Why Is a Forwarding Policy in the Faulty State?
- Why Can't I Add a Forwarding Policy to a Listener?
- Why Cannot I Select an Existing Backend Server Group When Adding a Forwarding Policy?
- Sticky Sessions
- Certificates
- Monitoring
- Change History
-
API Reference (Kuala Lumpur Region)
- Before You Start
- API Overview
- Calling APIs
- APIs
- Permissions Policies and Supported Actions
- Appendix
- Historical APIs
- Change History
-
User Guide (Ankara Region)
- Service Overview
- Load Balancer
- Listener
- Advanced Features of HTTP/HTTPS Listeners
- Backend Server Group
- Backend Server
- Certificate
- Access Control
- TLS Security Policy
- Access Logging
- Monitoring
- Quotas
-
FAQ
- Popular Questions
-
ELB Functionality
- Can ELB Be Used Separately?
- Does ELB Support Persistent Connections?
- Does ELB Support FTP on Backend Servers?
- Is an EIP Assigned Exclusively to a Load Balancer?
- How Many Load Balancers and Listeners Can I Have?
- What Types of APIs Does ELB Provide? What Are Permissions of ELB?
- Can I Adjust the Number of Backend Servers When a Load Balancer is Running?
- Can Backend Servers Run Different OSs?
- Can I Configure Different Backend Ports for a Load Balancer?
- Can ELB Be Used Across Accounts or VPCs?
- Can Backend Servers Access the Ports of a Load Balancer?
- Can Both the Listener and Backend Server Group Use HTTPS?
- Can I Change the VPC and Subnet for My Load Balancer?
-
Load Balancers
- How Does ELB Distribute Traffic?
- How Can I Access a Load Balancer Across VPCs?
- Do I Need to Configure EIP Bandwidth for My Load Balancers?
- Can I Bind Multiple EIPs to a Load Balancer?
- Why Multiple IP Addresses Are Required When I Create or Enable a Dedicated Load Balancer?
- Why Are Requests from the Same IP Address Routed to Different Backend Servers When the Load Balancing Algorithm Is Source IP Hash?
- Can Backend Servers Access the Internet Using the EIP of the Load Balancer?
- Will Traffic Routing Be Interrupted If the Load Balancing Algorithm Is Changed?
- What Is the Difference Between the Bandwidth Included in Each Specification of a Dedicated Load Balancer and the Bandwidth of an EIP?
-
Listeners
- What Are the Relationships Between Load Balancing Algorithms and Sticky Session Types?
- Can I Bind Multiple Certificates to a Listener?
- Will ELB Stop Distributing Traffic Immediately After a Listener Is Deleted?
- Does ELB Have Restrictions on the File Upload Speed and Size?
- Can Multiple Load Balancers Route Requests to One Backend Server?
- How Is WebSocket Used?
- Why Can't I Select the Target Backend Server Group When Adding or Modifying a Listener?
- Why Cannot I Add a Listener to a Dedicated Load Balancer?
-
Backend Servers
- Why Is the Interval at Which Backend Servers Receive Health Check Packets Different from What I Have Configured?
- Can Backend Servers Access the Internet After They Are Associated with a Load Balancer?
- Can ELB Route Traffic Across Regions?
- Does Each Backend Server Need an EIP to Receive Requests from a Public Network Load Balancer?
- How Do I Check the Network Conditions of a Backend Server?
- How Can I Check the Network Configuration of a Backend Server?
- How Do I Check the Status of a Backend Server?
- When Is a Backend Server Considered Healthy?
- Why Can I Access Backend Servers After a Whitelist Is Configured?
- When Will Modified Weights Take Effect?
- Why Must the Subnet Where the Load Balancer Resides Have at Least 16 Available IP Addresses for Enabling IP as a Backend?
-
Health Checks
- How Do I Troubleshoot an Unhealthy Backend Server?
- Why Is the Interval at Which Backend Servers Receive Health Check Packets Different from the Configured Interval?
- How Does ELB Perform UDP Health Checks? What Are the Precautions for UDP Health Checks?
- Why Does ELB Frequently Send Requests to Backend Servers During Health Checks?
- When Does a Health Check Start?
- Do Maximum Retries Include Health Checks That Consider Backend Servers Unhealthy?
- What Do I Do If a Lot of Access Logs Are Generated During Health Checks?
- What Status Codes Will Be Returned If Backend Servers Are Identified as Healthy?
- Obtaining Source IP Addresses
-
HTTP/HTTPS Listeners
- Which Protocol Should I Select for the Backend Server Group When Adding an HTTPS Listener?
- Why Is There a Security Warning After a Certificate Is Configured?
- Why Is a Forwarding Policy in the Faulty State?
- Why Can't I Add a Forwarding Policy to a Listener?
- Why Cannot I Select an Existing Backend Server Group When Adding a Forwarding Policy?
- Sticky Sessions
- Certificates
- Monitoring
- Change History
-
API Reference (Ankara Region)
- Before You Start
- API Overview
- Calling APIs
- APIs (V3)
- API (V2)
-
API (OpenStack API)
-
Tag
- Adding a Tag to a Load Balancer
- Batch Adding Load Balancer Tags
- Batch Deleting Load Balancer Tags
- Querying All Tags of a Load Balancer
- Querying the Tags of All Load Balancers
- Querying Load Balancers by Tag
- Deleting a Tag from a Load Balancer
- Adding a Tag to a Listener
- Batch Adding Tags to a Listener
- Batch Deleting Tags from a Listener
- Querying All Tags of a Listener
- Querying the Tags of All Listeners
- Querying Listeners by Tag
- Deleting a Tag from a Listener
- Status Codes
-
Tag
- Permissions and Supported Actions
- Appendix
- Change History
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Copied.
Creating a Dedicated Load Balancer
Scenarios
You have prepared everything required for creating a dedicated load balancer. For details, see Dedicated Load Balancer Overview.
Notes and Constraints
- After a dedicated load balancer is created, its VPC cannot be changed. If you want to change the VPC, create another load balancer and select a different VPC.
- To ping the IP address of a dedicated load balancer, you need to add a listener to it.
Procedure
- Go to the Buy Elastic Load Balancer page.
- On the load balancer list page, click Buy Elastic Load Balancer.
Complete the basic configurations 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.
Dedicated load balancers work well for heavy-traffic and high-concurrency workloads, such as large websites, cloud native applications, IoV, and multi-AZ disaster recovery applications.
For details about the differences, see Differences Between Dedicated and Shared Load Balancers.
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: postpaid billing mode. You pay as you go and just pay for what you use. The load balancer usage is calculated by the second but billed every hour.
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 where the dedicated load balancer works. An AZ is a part of a region and has its own independent power supplies and networks. AZs are physically isolated but interconnected through internal networks.
You can select multiple AZs for a load balancer to ensure high availability. If the load balancer in an AZ goes down, the load balancer in another AZ routes requests to backend servers to ensure service continuity and improve application reliability. For details about AZ planning, see AZ.
If you select multiple AZs for a load balancer, its performance, such as the number of new connections and the number of concurrent connections, will multiply by the number of AZs. For example, a dedicated load balancer in an AZ can handle 20 million concurrent connections. If you select two AZs for a dedicated load balancer, it can handle up to 40 million concurrent connections.
Name
Specifies the load balancer name. The name can contain:
- 1 to 64 characters.
- Letters, digits, underscores (_), hyphens (-), and periods (.).
Enterprise Project
Specifies an enterprise project by which cloud resources and members are centrally managed.
For details about creating and managing enterprise projects, see the Enterprise Management User Guide.
- Select specifications for the dedicated load balancer based on Table 2.
Table 2 Load balancer specifications Parameter
Description
Specifications
Select Elastic or Fixed if pay-per-use is chosen as the billing mode.
- Specification type
- 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.
- Load balancing type
- Application load balancing (HTTP/HTTPS): supports HTTP and HTTPS. This option is a great fit for workloads that require high performance at Layer 7, such as real-time audio and video, interactive livestreaming, and game applications.
- Networking load balancing (TCP/UDP/TLS): supports TCP, UDP, and TLS. This option is a great fit for heavy-traffic and high-concurrency workloads at Layer 4, such as file transfer, instant messaging, and online video applications.
Select either Application load balancing (HTTP/HTTPS) or Network load balancing (TCP/UDP/TLS) 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/TLS), respectively.
Select the desired specifications based on your service size. For details, see Specifications of Dedicated Load Balancers.
- Specification type
- Complete the network configurations based on Table 3.
Table 3 Configuring network parameters Parameter
Description
Network Type
Specifies the network where the load balancer works. You can select one or more network types.
- Private IPv4 network: The load balancer routes IPv4 requests from the clients to backend servers in a VPC. If you want the load balancer to route requests from the Internet, bind an EIP to the load balancer.
- 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 option, no IP address will be assigned to the load balancer. If this happens, 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.
VPC
Specifies the VPC where the dedicated load balancer works. You cannot change the VPC after the load balancer is created. Plan the VPC as required.
Select an existing VPC, or click View VPCs to create a desired one.
You can create a load balancer in a VPC subnet shared by another account for improved resource management and reduced O&M costs.
For more information about VPC sharing, see VPC Sharing in the Virtual Private Cloud User Guide.
Frontend Subnet
Specifies the frontend subnet from which an IP address will be assigned to the dedicated load balancer to receive client requests.
After a load balancer is created, you can unbind the IP address from it and assign an IP address from a new frontend subnet to the load balancer.
IP addresses in this subnet will be assigned to load balancers for receiving requests based on the configured network type.
- Private IPv4 network: IPv4 private addresses will be assigned.
- IPv6 network: IPv6 private or public addresses will be assigned.
NOTE:
If you select IPv6 network for Network Type and the selected VPC does not have any subnet that supports IPv6, enable IPv6 for at least one subnet or create a subnet that supports IPv6. For details, see the Virtual Private Cloud User Guide.
IPv4 Address
Specifies how you want the IPv4 address to be assigned if Network Type is set to Private IPv4 network.
- Automatically assign IP address: The system assigns an IPv4 address to the load balancer.
- Manually specify IP address: You need to manually specify an IPv4 address for the load balancer.
NOTE:
Network ACL rules configured for the frontend subnet of a load balancer do not restrict traffic from clients to the load balancer. Use access control to limit which IP addresses can access the load balancer.
For details, see What Is Access Control?
Backend Subnet
Specifies the backend subnet from which an IP address will be assigned to the dedicated load balancer to forward requests to backend servers.
- Subnet of the load balancer is selected by default.
- Select an existing subnet in the VPC where the load balancer works.
- Click Create Subnet on the right to create a new subnet.
NOTE:
- If you do not enable IPv6 for the specified backend subnet when you create a dedicated load balancer, the load balancer cannot use IPv6 addresses to route requests.
- The number of IP addresses required by a load balancer to communicate with the backend servers depends on how many AZs you have selected, how you configure the specifications, and whether you enable the IP as a backend option. See how many IP addresses are actually required 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.
IPv6 Address
Specifies how you want the IPv6 address to be assigned if Network Type is set to IPv6 network.
- Assign automatically: The system automatically assigns an IPv6 address to the load balancer.
- Manually specify: You need to manually specify an IPv6 address for the load balancer.
NOTE:
Network ACL rules configured for the frontend subnet of a load balancer do not restrict traffic from clients to the load balancer. Use access control to limit which IP addresses can access the load balancer.
For details, see What Is Access Control?
Shared Bandwidth
Specifies the shared bandwidth that the IPv6 address will be added to.
A shared bandwidth allows multiple EIPs in the same region to share the same bandwidth.
You can choose not to select a shared bandwidth, select an existing shared bandwidth, or buy a shared bandwidth.
IP as a Backend
Specifies whether to associate backend servers that are not in the VPC of the load balancer. After this option is enabled, you can associate the backend servers with the load balancer by using their IP addresses.
NOTE:
- To use this function, you need to configure correct VPC routes to ensure requests can be routed to backend servers.
- If you enable this option, more IP addresses in the backend subnet need to be reserved for the load balancer to communicate with backend servers. 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.
- Configure an EIP for the load balancer to enable it to route IPv4 requests over the Internet based on Table 4.
Table 4 Selecting an EIP for the load balancer Parameter
Description
EIP
Specifies the public IP address that will be bound to the load balancer for receiving and forwarding requests over the Internet.
- Auto assign: A new EIP will be assigned to the load balancer.
- Use existing: Select an existing EIP.
- Not required: You can bind an EIP to the load balancer later.
NOTE:
If you want to enable a load balancer to communicate with the Internet through a global EIP, you can bind a global EIP to the load balancer.
EIP Type
Specifies the link type (BGP) when a new EIP is used.
- Dynamic BGP: If there are changes on a network using dynamic BGP, routing protocols provide automatic, real-time optimization of network configurations, ensuring network stability and optimal user experience.
This option works well for workloads that require higher network stability and connectivity, such as financial transactions, online games, large-scale enterprise applications, and livestreaming services.
- Static BGP: If there are changes on a network using static BGP, carriers cannot adjust network configurations in real time to ensure optimal user experience.
This is a more cost-effective option for workloads that are running in relatively stable networks and have disaster recovery setups.
- EIP Pool: assigns EIPs with dynamic BGP routing, ensuring network stability and optimal user experience.
For details see What Are the Differences Between Static BGP and Dynamic BGP?
Billed By
Specifies how the bandwidth will be billed.
You can select one from the following options:
- Bandwidth: You specify the maximum bandwidth and pay for the amount of time you use the bandwidth.
- Traffic: You specify the maximum bandwidth and pay for the outbound traffic you use.
- Shared Bandwidth: Load balancers that have EIPs bound in the same region can share the selected bandwidth, helping you reduce public network bandwidth costs.
Bandwidth (Mbit/s)
Specifies the maximum bandwidth.
- Configure other parameters for the load balancer as described in Table 5.
Table 5 Configuring other parameters Parameter
Description
Advanced Settings (Optional) > Description
Click
to expand the configuration area and set this parameter.
Enter a description about the load balancer in the text box as required.
Enter up to 255 characters. Angle brackets (<>) are not allowed.
Advanced Settings (Optional) > Tag
Click
to expand the configuration area and set this parameter.
Add tags to the load balancer 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 6.
You can add a maximum of 20 tags.
Table 6 Tag key and value requirements Parameter
Requirement
Tag key
- Cannot be empty.
- Must be unique for the same load balancer.
- Can contain a maximum of 36 characters.
- Can contain only letters, digits, underscores (_), hyphens (-), at signs (@).
Tag value
- Can contain a maximum of 43 characters.
- Can contain only letters, digits, underscores (_), hyphens (-), at signs (@).
- Click Buy Now.
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