Server Load Balancer:Add an HTTPS listener

Step 1: Configure an HTTPS listener

1. Log on to the CLB console.
2. In the top navigation bar, select the region where the CLB instance is deployed.
3. Use one of the following methods to open the listener configuration wizard:
   • On the Instances page, find the CLB instance that you want to manage and click Configure Listener in the Actions column.
   • On the Instances page, click the ID of the CLB instance that you want to manage. On the Listeners tab, click Add Listener.
4. On the Protocol & Listener wizard page, set the following parameters and click Next.

   Parameter	Description
   Listener Protocol	Select the protocol of the listener. HTTPS is selected in this example.
   Backend Protocol	In this example, an HTTPS listener is required. Therefore, Backend Protocol is set to HTTP.
   Listener Port	Specify a listening port to receive requests and forward them to backend servers. Valid values: 1 to 65535.
   Listener Name	Specify a name for the listener.
   Advanced settings	Click Modify to configure advanced settings.
   Scheduling Algorithm	Select a scheduling algorithm. Weighted Round-Robin (WRR): Backend servers that have higher weights receive more requests than backend servers that have lower weights. Round-Robin (RR): Requests are distributed to backend servers in sequence.
   Enable Session Persistence	Specify whether to enable session persistence. After session persistence is enabled, CLB forwards all requests from a client to the same backend server. Cookie Persistence: Insert cookie: If you select this option, you need to only specify the timeout period of the cookie. CLB inserts a cookie (SERVERID) into the first HTTP or HTTPS response that is sent to a client. The next request from the client carries this cookie, and the listener will forward this request to the recorded backend server. Persistent Timeout: If you select Insert cookie, you must specify the timeout period for session persistence. Valid values: 1 to 86400. Unit: seconds. Rewrite cookie: If you select this option, you can specify the cookie that you want to insert into an HTTP or HTTPS response. In this case, you must specify the timeout period and lifetime of a cookie on a backend server. After you specify a cookie, CLB overwrites the original cookie with the specified cookie. The next time CLB receives a client request that carries the specified cookie, the listener distributes the request to the recorded backend server. Cookie Name: If you select Rewrite cookie, you must specify a name for the cookie.
   Enable HTTP/2	Select whether to enable HTTP/2 support for the CLB instance.
   Enable Access Control	Specify whether to enable access control. Select an access control method after you enable access control. Then, select a network access control list (ACL) as the whitelist or blacklist of the listener. Whitelist: allows access from specific IP addresses. Only requests from the IP addresses or CIDR blocks specified in the network ACL are forwarded. Whitelists apply to scenarios in which you want to allow access only from specific IP addresses. Your service may be adversely affected if the whitelist is not properly configured. After a whitelist is configured, only requests from IP addresses that are added to the whitelist are forwarded by the listener. If a whitelist is configured but no IP address is added to the whitelist, the listener forwards all requests. Blacklist: denies access from specific IP addresses. Requests from the IP addresses or CIDR blocks specified in the network ACL are denied. Blacklists apply to scenarios in which you want to deny access from specific IP addresses. If a blacklist is configured but no IP address is added to the blacklist, the listener forwards all requests. Note IPv6 instances can be associated only with IPv6 network ACLs, and IPv4 instances can be associated only with IPv4 network ACLs. For more information, see Create a network ACL.
   Enable Peak Bandwidth Limit	Specify whether to set the bandwidth limit of the listener. If the CLB instance is billed based on bandwidth usage, you can set different maximum bandwidth values for different listeners. This limits the amount of traffic that can be forwarded by each listener. The sum of the maximum bandwidth of all listeners that are added to a CLB instance cannot exceed the maximum bandwidth of the CLB instance. By default, this feature is disabled and all listeners share the bandwidth of the CLB instance. Note If a pay-by-data-transfer CLB instance is used, the bandwidth of its listeners is not limited by default.
   Idle Timeout	Specify a timeout period for idle connections. Unit: seconds. Valid values: 1 to 60. If no request is received within the specified timeout period, CLB closes the connection. When another request is received, CLB establishes a new connection.
   Connection Request Timeout	Specify a request timeout period. Unit: seconds. Valid values: 1 to 180. If no response is received from a backend server within the specified timeout period, CLB returns the HTTP 504 status code to the client.
   Gzip Compression	If you enable Gzip compression, files of specific types are compressed. If you disable Gzip compression, no file is compressed. Gzip supports the following file types: text/xml, text/plain, text/css, application/javascript, application/x-javascript, application/rss+xml, application/atom+xml, and application/xml.
   Add HTTP Header Fields	Supported headers: X-Forwarded-For: Add the header to retrieve client IP addresses. SLB-ID: Add the header to retrieve the ID of the CLB instance. SLB-IP: Add the header to retrieve the IP address of the CLB instance. X-Forwarded-Proto: Add the header to retrieve the listening protocol. X-Forwarded-Port: Add the header to retrieve the listening port. X-Forwarded-Client-srcport: Add the header to retrieve client ports.
   Client IP Address Preservation	Specify whether to retrieve client IP addresses. By default, this feature is enabled.
   Automatically Enable Listener	Specify whether to immediately enable the listener after it is created. By default, listeners are enabled after they are created.
   WAF Protection	Specify whether to enable Web Application Firewall (WAF) protection for the listener.

Step 2: Configure an SSL certificate

When you add an HTTPS listener, you must upload a server certificate or certificate authority (CA) certificate and select a TLS security policy, as shown in the following table.

1. On the SSL Certificates wizard page, select the server certificate that you uploaded. You can also click Create Server Certificate to upload a server certificate.
2. Optional:Click Modify next to Advanced to enable mutual authentication or configure a TLS security policy.
   1. Enable mutual authentication and select an existing CA certificate. You can also upload a CA certificate. For more information, see Create a private CA.
   2. For more information about TLS security policies, see TLS security policies.

Step 3: Add backend servers

After the listener is created, you must add backend servers to process client requests. You can add backend servers to the default server group, or create vServer groups or primary/secondary server groups and then add servers to the server groups. For more information, see Backend server overview.

In this example, backend servers are added to the default server group.

1. On the Backend Servers wizard page, select Default Server Group. Then, click Add More.
2. In the My Servers panel, select the Elastic Compute Service (ECS) instances that you want to add as backend servers and click Next.
3. Set weights for the selected ECS instances in the Weight column.
   Note

   • An ECS instance with a higher weight receives more requests. The default weight is 100. You can click Reset to set Weight to the default value.
   • If you set the weight of a server to 0, the server does not receive requests.
4. Click Add. Specify the ports for backend servers to receive requests. Valid values: 1 to 65535. Click Next.

   You can specify the same port for backend servers that are added to a CLB instance.

Step 4: Configure health checks

CLB checks the availability of backend ECS instances by performing health checks. The health check feature improves service availability and prevents service interruptions caused by single points of failure.

1. Optional:On the Health Check wizard page, click Modify to modify the health check configurations.
   For more information, see Configure health check.
2. Click Next.

Step 5: Submit the configurations

1. On the Confirm Configurations wizard page, confirm the configurations. You can click Modify to modify the configurations.
2. After you confirm the configurations, click Submit.
3. After the configurations are submitted, click OK.

   After you configure the listener, you can view the listener on the Listener tab.

References

• Add an ECS instance to the default server group
• Create and manage a vServer group
• Create and manage a primary/secondary server group
• Overview
• Forward requests based on domain names or URLs
• Add an additional certificate
• CreateLoadBalancerHTTPSListener: creates an HTTPS listener.