Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
Software Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Listener Overview

Updated on 2024-11-14 GMT+08:00

A listener checks requests from clients and routes requests to backend servers using the protocol, port, and load balancing algorithm you select. You need to add at least one listener after you have created a load balancer.

Supported Protocols and Application Scenarios

ELB provides load balancing at both Layer 4 and Layer 7.

You can select TCP, TLS, or UDP for network load balancing and HTTP or HTTPS for application load balancing.

Table 1 Protocols supported by ELB

Type

Protocol

Description

Application Scenario

Network listeners

TCP

  • Source IP address–based sticky sessions
  • Fast data transfer
  • Scenarios that require high reliability and data accuracy, such as file transfer, email, and remote login
  • Web applications that do not need to handle a large number of concurrent requests and do not require high performance

Network listeners

UDP

  • Relatively low reliability
  • Fast data transfer

Scenarios that require quick response, such as video chat, gaming, and real-time financial quotations

Network listeners

TLS

  • An extension of HTTP for encrypted data transmission that can prevent unauthorized access
  • Unidirectional/Bidirectional authentication

Scenarios that require ultra-high performance and large-scale TLS offloading

Application listeners

HTTP

  • Cookie-based sticky sessions
  • X-Forward-For request header

Applications that require content identification, for example, web applications and mobile games

Application listeners

HTTPS

  • An extension of HTTP for encrypted data transmission that can prevent unauthorized access
  • Encryption and decryption performed on load balancers
  • Multiple versions of encryption protocols and cipher suites

Workloads that require encrypted transmission, such as e-commerce and financial services.

NOTE:

TLS listeners will be available in more regions. See details on the management console.

Frontend Protocols and Ports

Frontend protocols and ports are used by load balancers to receive requests from clients.

Load balancers use TCP, TLS, or UDP for network load balancing, and HTTP or HTTPS for application load balancing. Select a protocol and a port that best suit your requirements.

NOTE:

The frontend protocols and ports cannot be changed once a listener is added. If you want to use a different protocol and port, add another listener.

Table 2 Frontend protocols and ports

Frontend Protocol

TCP, UDP, TLS, HTTP, or HTTPS

Frontend Port

Listeners using different protocols of a load balancer cannot use the same port. However, UDP listeners can use the same port as listeners that use other protocols. For example, if there is a UDP listener that uses port 88, you can add a TCP listener that also uses port 88. The port number ranges from 1 to 65535.

The following are some commonly-used protocols and port numbers:

  • TCP/80
  • HTTPS/443

Backend Protocols and Ports

Backend protocols and ports are used by backend servers to receive requests from load balancers. If Windows servers have Internet Information Services (IIS) installed, the default backend protocol and port are HTTP and 80.

Table 3 Backend protocols and ports

Backend Protocol

TCP, UDP, TLS, HTTP, HTTPS, or QUIC

Backend Port

Backend servers of a load balancer can use the same ports. The port number ranges from 1 to 65535.

The following are some commonly-used protocols and port numbers:

  • TCP/80
  • HTTP/80
  • HTTPS/443

Forwarding by Port Ranges

Forwarding by Port Ranges is available only when you select TCP or UDP as the frontend protocol.

If this option is enabled, the listener checks requests from all ports in the port range you specify and routes them to the corresponding ports on the backend servers.

Timeout Durations

You can configure and modify timeout durations for your listeners to meet varied demands. For example, if the size of a request from an HTTP or HTTPS client is large, you can prolong the request timeout duration to ensure that the request can be successfully routed.

Figure 1 Timeout durations at Layer 4
Figure 2 Timeout durations at Layer 7
Table 4 Timeout durations

Protocol

Type

Description

Value Range

Default Timeout Duration

TCP

Idle Timeout

Duration for a connection to keep alive. If no request is received within this period, the load balancer closes the connection and establishes a new one with the client when the next request arrives.

10–4000s

300s

UDP

Idle Timeout

10–4000s

300s

HTTP/HTTPS

Idle Timeout

0–4000s

60s

Request Timeout

Duration that a load balancer is willing to wait for a client request to complete. The load balancer terminates the connection if a request takes too long to complete.

1–300s

60s

Response Timeout

Duration after which the load balancer sends a 504 Gateway Timeout error to the client if the load balancer receives no response after routing a request to a backend server and receives no response after attempting to route the same request to other backend servers.

NOTE:

If you have enabled sticky sessions and the backend server does not respond within the response timeout duration, the load balancer returns 504 Gateway Timeout to the clients.

1–300s

60s

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback