Docs

Load Balancer

Creating a listener

Creating an HTTP listener

This topic introduces how to create an HTTP listener in the ALB console. HTTP listeners are suitable for scenarios that do not involve sensitive information transmission and require data content identification.

Each ALB instance must have at least one listener to function properly. A listener accepts client requests and distributes them to backend servers based on the forwarding rules and load balancing algorithms you configure. You can create multiple listeners under a single ALB instance and configure them with different listener protocols to handle client requests using different protocols.

Prerequisites

You have created an ALB instance.

You have created the required server group.

Procedures

In the top menu bar, select the target project and region.

Click Listener to the right of the target ALB instance.

On the Listeners tab, click Add listener.

Configure relevant parameters based on the table below.

Parameter	Explanation	Example
Name	Enter the listener name. Naming rules are as follows: Can contain English letters, Chinese characters, numbers, half-width period (.), underscore (_), and hyphen (-). Must start with an English letter or a Chinese character. Cannot start with http:// or https://. A maximum of 128 characters is allowed. If left blank, it defaults to Protocol-port, such as HTTP-80.	HTTP-80
Listening protocol	Set the listening protocol to HTTP. HTTP listeners support the WebSocket protocol by default and do not require additional enabling.	HTTP
Listening port	Set the port for the listener. Valid range: 1-65535. The ports for different listeners under the same ALB instance must be unique.	80
Access control	Whether to enable the Access Control feature for the listener to allow or deny requests from specific clients. If the access control feature is not enabled, requests from all clients will be allowed.	Check
Control mode	Configure access control mode. After enabling Access Control, you must select access control mode. Allowlist: Only IP addresses within the selected policy group will be permitted access to the listener. Denylist: IP addresses within the selected policy group will be denied access to the listener.	Denylist
Policy group	Select policy group. After enabling Access Control, you must configure a policy group. A maximum of 5 policy groups can be selected. Each policy group can contain up to 300 IP address entries. Each IP address entry can be a single IP address or a CIDR block. For more information about policy groups, see Access Control.
Tags	A tag consists of a key-value pair and is used for categorizing and searching resources Prerequisite Click the Add icon, input the tag key and tag value, and add a tag for the listener.	Tag key: alb-http Tag value: http-80

Click Next: default backend server group.

On the Default server group tab, select the prepared server group from the dropdown, then click Next: confirm the configuration.

After confirming the listener configuration information is correct, click Save.

What to do next

Configure personalized settings: allows you to customize configuration items such as long connection retention time, timeout, maximum client request body size, custom response headers, and custom request headers.

Configure forwarding rules: ALB distributes access traffic based on the forwarding rules you set for different traffic characteristics.

Last updated: 2026.06.17 14:10:36