Updated on 2026-11-05 GMT+08:00

Fast Adding a Listener

Generally, you must configure all listener parameters manually. This process is relatively complex. In some service scenarios, you only need to configure mandatory listener parameters and keep the default values for optional ones. You can use the Fast-Add Listener function to simplify the process and save time.

The Fast-Add Listener function displays only mandatory parameters for you to configure, retains default values for optional ones, and hides optional parameters from the listener-adding page. Listeners added through the regular process and those added through the Fast-Add Listener function can be managed in the same way.

On the Fast-Add Listener page, you can click Create Backend Server Group to fast create a backend server group. Only mandatory parameters are displayed for configuration, while optional parameters are set to default values and hidden from the creation page. Backend server groups created through the regular process and those created in a fast way can be managed in the same way.

Fast Adding a TCP Listener

  1. Go to the load balancer list page.
  2. In the load balancer list, locate the target load balancer and click its name.
  3. Under Listeners, click Fast-Add Listener.
    Configure the parameters based on Table 1.
    Table 1 Parameters for configuring a TCP listener for a dedicated load balancer

    Parameter

    Description

    Frontend Protocol

    Specifies the protocol used by the load balancer's listener to receive requests from the clients.

    Select TCP.

    Listening Port

    Specifies the port or port ranges used by the load balancer to receive requests from clients.

    Backend Server Group

    Specifies the default backend server group for the listener.

  4. Confirm the configuration and click OK.

Fast Adding a UDP Listener

  1. Go to the load balancer list page.
  2. In the load balancer list, locate the target load balancer and click its name.
  3. Under Listeners, click Fast-Add Listener.
    Configure the parameters based on Table 2.
    Table 2 Parameters for configuring a UDP listener for a dedicated load balancer

    Parameter

    Description

    Frontend Protocol

    Specifies the protocol used by the load balancer's listener to receive requests from the clients.

    Select UDP.

    Listening Port

    Specifies the port or port ranges used by the load balancer to receive requests from clients.

    Backend Server Group

    Specifies the default backend server group for the listener.

  4. Confirm the configuration and click OK.

Fast Adding a TLS Listener

  1. Go to the load balancer list page.
  2. In the load balancer list, locate the target load balancer and click its name.
  3. Under Listeners, click Fast-Add Listener.
    Configure the parameters based on Table 3.
    Table 3 Parameters for configuring a TLS listener for a dedicated load balancer

    Parameter

    Description

    Frontend Protocol

    Specifies the protocol used by the load balancer's listener to receive requests from the clients.

    Select TLS.

    Listening Port

    Specifies the port or port ranges used by the load balancer to receive requests from clients.

    SSL Authentication

    Specifies how you want the clients and backend servers to be authenticated.

    • One-way authentication: Backend servers will be authenticated by clients.
    • Mutual authentication: The clients and backend servers will authenticate each other.

    CA Certificate

    Specifies the certificate that will be used to authenticate the client when SSL Authentication is set to Mutual authentication.

    CA certificates are also called client CA public key certificates. They are used to verify the issuer of a client certificate. HTTPS connections can only be established when the client provides a certificate issued by a specific CA.

    Server Certificate

    Specifies a server certificate that will be used to authenticate the server when TLS is used as the frontend protocol.

    Both the certificate and private key are required.

    SNI

    Server Name Indication (SNI) is a TLS extension that enables a client to specify the requested domain name during the handshake. This allows a listener hosting multiple domain names to select the correct certificate based on the domain name in the request.

    The client includes the domain name in the initial SSL handshake. Once receiving the request, the load balancer searches for the certificate based on the domain name.

    If an SNI certificate is found, this certificate will be used for authentication.

    If no SNI certificate is found, the server certificate is used for authentication.

    For details, see Using SNI Certificates for Access Through Multiple Domain Names.

    SNI Certificate

    Specifies one or more certificates associated with the domain name when the frontend protocol is TLS and SNI is enabled.

    You can only select server certificates with SNI domain names.

    Backend Server Group

    Specifies the default backend server group for the listener.

  4. Confirm the configuration and click OK.

Fast Adding an HTTP Listener

  1. Go to the load balancer list page.
  2. In the load balancer list, locate the target load balancer and click its name.
  3. Under Listeners, click Fast-Add Listener.
    Configure the parameters based on Table 4.
    Table 4 Parameters for configuring an HTTP listener for a dedicated load balancer

    Parameter

    Description

    Frontend Protocol

    Specifies the protocol used by the load balancer's listener to receive requests from the clients.

    Select HTTP.

    Listening Port

    Specifies the port or port ranges used by the load balancer to receive requests from clients.

    Backend Server Group

    Specifies the default backend server group for the listener.

  4. Confirm the configuration and click OK.

Fast Adding an HTTPS Listener

  1. Go to the load balancer list page.
  2. In the load balancer list, locate the target load balancer and click its name.
  3. Under Listeners, click Fast-Add Listener.
    Configure the parameters based on Table 5.
    Table 5 Parameters for configuring an HTTPS listener for a dedicated load balancer

    Parameter

    Description

    Frontend Protocol

    Specifies the protocol used by the load balancer's listener to receive requests from the clients.

    Select HTTPS.

    Listening Port

    Specifies the port or port ranges used by the load balancer to receive requests from clients.

    SSL Authentication

    Specifies how you want the clients and backend servers to be authenticated.

    • One-way authentication: Backend servers will be authenticated by clients.
    • Mutual authentication: The clients and backend servers will authenticate each other.

    CA Certificate

    Specifies the certificate that will be used to authenticate the client when SSL Authentication is set to Mutual authentication and the frontend protocol is HTTPS.

    CA certificates are also called client CA public key certificates. They are used to verify the issuer of a client certificate. HTTPS connections can only be established when the client provides a certificate issued by a specific CA.

    Server Certificate

    Specifies a server certificate that will be used to authenticate the server when HTTPS is used as the frontend protocol.

    The server certificate is used for SSL handshake. Both the certificate and private key are required.

    SNI

    Server Name Indication (SNI) is a TLS extension that enables a client to specify the requested domain name during the handshake. This allows a listener hosting multiple domain names to select the correct certificate based on the domain name in the request.

    The client includes the domain name in the initial SSL handshake. Once receiving the request, the load balancer searches for the certificate based on the domain name.

    If an SNI certificate is found, this certificate will be used for authentication.

    If no SNI certificate is found, the server certificate is used for authentication.

    For details, see Using SNI Certificates for Access Through Multiple Domain Names.

    SNI Certificate

    Specifies one or more certificates associated with the domain name when the frontend protocol is TLS and SNI is enabled.

    You can only select server certificates with SNI domain names.

    Backend Server Group

    Specifies the default backend server group for the listener.

  4. Confirm the configuration and click OK.

Fast Adding a QUIC Listener

  1. Go to the load balancer list page.
  2. In the load balancer list, locate the target load balancer and click its name.
  3. Under Listeners, click Fast-Add Listener.
    Configure the parameters based on Table 6.
    Table 6 Parameters for configuring a QUIC listener for a dedicated load balancer

    Parameter

    Description

    Frontend Protocol

    Specifies the protocol used by the load balancer's listener to receive requests from the clients.

    Select QUIC.

    Listening Port

    Specifies the port or port ranges used by the load balancer to receive requests from clients.

    Server Certificate

    Specifies a server certificate that will be used to authenticate the server. One-way authentication is used by default for QUIC listeners.

    Both the certificate and private key are required. For details, see Adding a Certificate.

    SNI

    Server Name Indication (SNI) is a TLS extension that enables a client to specify the requested domain name during the handshake. This allows a listener hosting multiple domain names to select the correct certificate based on the domain name in the request.

    The client includes the domain name in the initial SSL handshake. Once receiving the request, the load balancer searches for the certificate based on the domain name.

    If an SNI certificate is found, this certificate will be used for authentication.

    If no SNI certificate is found, the server certificate is used for authentication.

    For details, see Using SNI Certificates for Access Through Multiple Domain Names.

    SNI Certificate

    Specifies one or more certificates associated with the domain name when the frontend protocol is TLS and SNI is enabled.

    You can only select server certificates with SNI domain names.

    Backend Server Group

    Specifies the default backend server group for the listener.

  4. Confirm the configuration and click OK.

Fast Creating a Backend Server Group

The function of fast creating a backend server group is typically used with the Fast-Add Listener function and is not recommended for independent use. During the creation, some parameters are automatically obtained from the load balancer that the listener was fast added for, such as the type, load balancer, and VPC.

  1. On the Fast-Add Listener page, click Create Backend Server Group next to the backend server group selection box to fast create a backend server group.
    Configure the backend server group based on Table 7.
    Table 7 Backend server group parameters

    Parameter

    Description

    Backend Server Group Name

    Specifies the name of the backend server group.

    Enterprise Project

    Specifies an enterprise project by which backend server groups can be centrally managed.

    An enterprise project facilitates project-level management and grouping of cloud resources and users.

    For details about creating and managing enterprise projects, see the Enterprise Management User Guide.

    Backend Server Group Type

    Specifies the type of the backend server group.

    • Hybrid: You can add cloud servers and supplementary network interfaces as backend servers, and add IP addresses as backend servers when IP as a Backend is enabled.
    • IP as a backend server: You can add IP addresses as backend servers.

      This function is available only when IP as a Backend is enabled.

    NOTE:

    This function is available in certain regions. You can see which regions support this function on the console.

    Backend Protocol

    Specifies the protocol that backend servers in the backend server group use to receive requests from the listeners. The protocol varies depending on the forwarding mode:

    • Load balancing: HTTP, HTTPS, gRPC, TCP, UDP, TLS, or QUIC
    • Active/Standby: TCP, UDP, TLS, or QUIC

    IP Address Version

    Specifies the IP address version of backend servers that can be added to the backend server group. By default, IPv4 backend servers are supported.

    There are two options when the backend protocol is TCP or UDP:

    • IPv4: Only IPv4 addresses can be added as backend servers.
    • Dual stack: Both IPv4 and IPv6 addresses can be added as backend servers.
    NOTE:

    This option is available in certain regions. You can see which regions support this option on the console.

    Load Balancing Algorithm

    Specifies the algorithm used by the load balancer to distribute traffic. The following options are available:

    • Weighted round robin: Requests are routed to different servers based on their weights. Backend servers with higher weights receive proportionately more requests, whereas equal-weighted servers receive the same number of requests.
    • Weighted least connections: In addition to the number of connections, each server is assigned a weight based on its capacity. Requests are routed to the server with the lowest connections-to-weight ratio.
    • Source IP hash: Requests from different clients are routed based on source IP addresses and requests from the same client are forwarded to the same server.
    • Connection ID: This algorithm is available when you have selected QUIC for Backend Protocol. This algorithm allows requests with the same connection ID to be routed to the same backend server.

    For more information about load balancing algorithms, see Configuring Load Balancing Algorithms to Distribute Traffic.

    Health Check

    Select Health Check to enable it.

    Health Check checks server availability and ensures that requests are routed only to healthy backend servers.

  2. Confirm the configuration and click OK.