El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.
- 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
- 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.
Using ELB to Redirect HTTP Requests to an HTTPS Listener for Higher Service Security
Scenarios
HTTPS is an extension of HTTP. HTTPS encrypts data between a web server and a browser. You can use ELB to redirect HTTP requests to an HTTPS listener to improve your service security.
- If the listener protocol is HTTP, only the GET or HEAD method can be used for redirection. If you create a redirect for an HTTP listener, the client browser will change POST or other methods to GET. If you want to use other methods rather than GET and HEAD, add an HTTPS listener.
- HTTP requests are forwarded to the HTTPS listener as HTTPS requests, which are then routed to backend servers over HTTP.
- If HTTP requests are redirected to an HTTPS listener, no certificate can be deployed on the backend servers associated with the HTTPS listener. If certificates are deployed, HTTPS requests will not take effect.
Prerequisites
- You have created a dedicated load balancer. For details, see Creating a Dedicated Load Balancer.
- You have created two ECSs (ECS_client and ECS_server) that are running in the same VPC as the dedicated load balancer. ECS_client sends HTTP requests, while ECS_server processes requests. For details, see Purchasing an ECS.
- You have gotten a server certificate ready for adding an HTTPS listener. For details, see Adding a Server Certificate.
Procedure
Step 1: Create an HTTPS Listener
- Go to the load balancer list page.
- On the displayed page, locate the target load balancer and click its name.
- On the Listeners tab, click Add Listener. Configure the parameters based on Table 1.
Figure 2 Adding an HTTPS listener
Table 1 Parameters for configuring an HTTPS listener Parameter
Example Value
Description
Name
listener-HTTPS
Specifies the listener name.
Frontend Protocol
HTTPS
Specifies the protocol that will be used by the load balancer to receive requests from clients.
Frontend Port
443
Specifies the port that will be used by the load balancer to receive requests from clients.
SSL Authentication
One-way authentication
Specifies how you want the clients and backend servers to be authenticated. In this practice, One-way authentication is selected.
Server Certificate
The existing server certificate
Specifies the certificate that will be used by the backend server for SSL handshake negotiation to authenticate clients and ensure encrypted transmission.
Enable SNI
Not enabled
Specifies whether to enable SNI when HTTPS is used as the frontend protocol. SNI can be used when a server uses multiple domain names and certificates.
Access Control
All IP addresses
Specifies how access to the listener is controlled. Access from specific IP addresses can be controlled using a whitelist or blacklist.
Transfer Client IP Address
Enabled by default
Specifies whether to transmit IP addresses of the clients to backend servers.
Advanced Forwarding
Enabled
Specifies whether to enable the advanced forwarding policy. You can add advanced forwarding policies to HTTP or HTTPS listeners to forward requests to different backend server groups.
- Retain the default values for parameters under Advanced Settings and click Next: Configure Request Routing Policy.
- Select Create new for Backend Server Group, retain the default values for other parameters, and click Next: Add Backend Server.
- Add ECS_server to the backend server group you have created, enable Health Check, and retain the default values for the health check.
- Click Next: Confirm and then click Submit.
Step 2: Configure HTTP to HTTPS Redirection
You can enable redirection when adding an HTTP listener and select an HTTPS listener to which requests are redirected. Alternatively, you can add a forwarding policy for an HTTP listener to redirect requests to an HTTPS listener.
- 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, locate the target load balancer and click its name.
- On the Listeners tab, click Add Listener. Configure the parameters based on Table 2.
Figure 3 Adding an HTTP Listener
Table 2 Parameters for configuring an HTTP listener Parameter
Example Value
Description
Name
listener-HTTP
Specifies the listener name.
Frontend Protocol
HTTP
Specifies the protocol that will be used by the load balancer to receive requests from clients.
Frontend Port
80
Specifies the port that will be used by the load balancer to receive requests from clients.
Redirect
Enabled
Specifies whether to enable redirection. You can use this function to redirect the requests from an HTTP listener to an HTTPS listener to ensure security.
Redirected To
listener-HTTPS
Specifies the HTTPS listener to which requests are redirected. Select the HTTPS listener created in section Step 1: Create an HTTPS Listener, listener-HTTPS.
Access Control
All IP addresses
Specifies how access to the listener is controlled. Access from specific IP addresses can be controlled using a whitelist or blacklist.
Transfer Client IP Address
Enabled by default
Specifies whether to transmit IP addresses of the clients to backend servers.
Advanced Forwarding
Enabled
Specifies whether to enable the advanced forwarding policy. You can add advanced forwarding policies to HTTP or HTTPS listeners to forward requests to different backend server groups.
- Retain the default values for parameters under Advanced Settings and click Next: Confirm.
- Click Submit.
- 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, locate the target load balancer and click its name.
- On the Listeners tab, click Add Listener. Configure the parameters based on Table 3.
Figure 4 Adding an HTTP Listener
Table 3 Parameters for configuring an HTTP listener Parameter
Example Value
Description
Name
listener-HTTP
Specifies the listener name.
Frontend Protocol
HTTP
Specifies the protocol that will be used by the load balancer to receive requests from clients.
Frontend Port
80
Specifies the port that will be used by the load balancer to receive requests from clients.
Redirect
Not enabled
Specifies whether to enable redirection. You can use this function to redirect the requests from an HTTP listener to an HTTPS listener to ensure security.
Access Control
All IP addresses
Specifies how access to the listener is controlled. Access from specific IP addresses can be controlled using a whitelist or blacklist.
Transfer Client IP Address
Enabled by default
Specifies whether to transmit IP addresses of the clients to backend servers.
Advanced Forwarding
Enabled
Specifies whether to enable the advanced forwarding policy. You can add advanced forwarding policies to HTTP or HTTPS listeners to forward requests to different backend server groups.
- Retain the default values for parameters under Advanced Settings and click Next: Configure Request Routing Policy.
- Select Create new for Backend Server Group, retain the default values for other parameters, and click Next: Add Backend Server.
- Add ECS_server to the backend server group you have created, enable Health Check, and retain the default values for the health check.
- Click Next: Confirm and then click Submit.
- On the Configuration Result page, click Add now under the Next: Add a Forwarding Policy (Optional) area.
- Click Add Forwarding Policy to configure redirection.
Table 4 Configuring parameters for redirection Parameter
Setting
Action
Select Redirect to another listener.
Listener
Select the HTTPS listener to which requests are redirected.
- After the forwarding policy is added, click Save.
Figure 5 Redirection to an HTTPS listener
- 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, locate the target load balancer and click its name.
- On the Listeners tab, click Add Listener. Configure the parameters based on Table 2.
Figure 3 Adding an HTTP Listener
Table 2 Parameters for configuring an HTTP listener Parameter
Example Value
Description
Name
listener-HTTP
Specifies the listener name.
Frontend Protocol
HTTP
Specifies the protocol that will be used by the load balancer to receive requests from clients.
Frontend Port
80
Specifies the port that will be used by the load balancer to receive requests from clients.
Redirect
Enabled
Specifies whether to enable redirection. You can use this function to redirect the requests from an HTTP listener to an HTTPS listener to ensure security.
Redirected To
listener-HTTPS
Specifies the HTTPS listener to which requests are redirected. Select the HTTPS listener created in section Step 1: Create an HTTPS Listener, listener-HTTPS.
Access Control
All IP addresses
Specifies how access to the listener is controlled. Access from specific IP addresses can be controlled using a whitelist or blacklist.
Transfer Client IP Address
Enabled by default
Specifies whether to transmit IP addresses of the clients to backend servers.
Advanced Forwarding
Enabled
Specifies whether to enable the advanced forwarding policy. You can add advanced forwarding policies to HTTP or HTTPS listeners to forward requests to different backend server groups.
- Retain the default values for parameters under Advanced Settings and click Next: Confirm.
- Click Submit.
- 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, locate the target load balancer and click its name.
- On the Listeners tab, click Add Listener. Configure the parameters based on Table 3.
Figure 4 Adding an HTTP Listener
Table 3 Parameters for configuring an HTTP listener Parameter
Example Value
Description
Name
listener-HTTP
Specifies the listener name.
Frontend Protocol
HTTP
Specifies the protocol that will be used by the load balancer to receive requests from clients.
Frontend Port
80
Specifies the port that will be used by the load balancer to receive requests from clients.
Redirect
Not enabled
Specifies whether to enable redirection. You can use this function to redirect the requests from an HTTP listener to an HTTPS listener to ensure security.
Access Control
All IP addresses
Specifies how access to the listener is controlled. Access from specific IP addresses can be controlled using a whitelist or blacklist.
Transfer Client IP Address
Enabled by default
Specifies whether to transmit IP addresses of the clients to backend servers.
Advanced Forwarding
Enabled
Specifies whether to enable the advanced forwarding policy. You can add advanced forwarding policies to HTTP or HTTPS listeners to forward requests to different backend server groups.
- Retain the default values for parameters under Advanced Settings and click Next: Configure Request Routing Policy.
- Select Create new for Backend Server Group, retain the default values for other parameters, and click Next: Add Backend Server.
- Add ECS_server to the backend server group you have created, enable Health Check, and retain the default values for the health check.
- Click Next: Confirm and then click Submit.
- On the Configuration Result page, click Add now under the Next: Add a Forwarding Policy (Optional) area.
- Click Add Forwarding Policy to configure redirection.
Table 4 Configuring parameters for redirection Parameter
Setting
Action
Select Redirect to another listener.
Listener
Select the HTTPS listener to which requests are redirected.
- After the forwarding policy is added, click Save.
Figure 5 Redirection to an HTTPS listener
- After the redirection is added, the configurations for the HTTP listener will not be applied, but access control configured for that listener will still be applied.
- After the redirection is added for an HTTP listener, the backend server will return 301 Moved Permanently to the clients.
Step 3: Verify the Redirection to HTTPS
Remotely log in to ECS_client and run curl -H "Accept-Language: zh-CN,zh" "http://ELB-private-IP-address:80 to check whether HTTP requests are redirected.
If 301 Moved Permanently is returned, as shown in the below figure, HTTP requests are directed to an HTTP listener.
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