Server Load Balancer:Add a QUIC listener

Step 1: Create a listener

To create a QUIC listener, perform the following steps:

1. Log on to the ALB console.

2. Use one of the following methods to open the listener configuration wizard:

   • On the Instances page, find the ALB instance that you want to manage and click Actions in the Create Listener column.

   • On the Instances page, click the ID of the NLB instance that you want to manage. On the Listener tab, click Create Listener.

3. On the Configure Listener wizard page, set the following parameters and click Next.

   Parameter	Description
   Listener Protocol	Select a listener protocol. In this example, QUIC is selected.
   Listener Port	Select the port on which the ALB instance listens. The ALB instance listens on the port and forwards requests to backend servers. Valid values: 1 to 65535. Note On the same ALB instance, the ports of listeners that use the same protocol must be unique. HTTP listeners and HTTPS listeners must use different ports.
   Listener Name	Enter a name for the listener.
   Tag	Configure the Tag Key and Tag Value parameters to add a tag. You can add one or more tags. After you specify tags, you can filter listeners by tag on the Listener tab.
   Advanced Settings	You can click Modify to configure the advanced settings.
   Idle Connection Timeout Period	Specify a timeout period for idle connections. Unit: seconds. Valid values: 1 to 600. Default value: 15. To specify a longer timeout period, go to the Quota Center console. If no request is received within the specified timeout period, ALB closes the connection. When another request is received, ALB establishes a new connection.
   Connection Request Timeout	Specify a request timeout period. Unit: seconds. Valid values: 1 to 600. Default value: 60. To specify a longer timeout period, go to the Quota Center console. If no response is received from the backend server within the request timeout period, ALB returns the HTTP 504 error code to the client.
   Compression	If you enable compression, specific types of files are compressed. If you disable compression, no file is compressed. Brotli supports all file types. GZIP supports the following file types: text/xml, text/plain, text/css, application/javascript, application/x-javascript, application/rss+xml, application/atom+xml, application/xml, and application/json. Note If a client request allows both Brotli and GZIP compression, ALB will use Brotli compression which is more efficient. If a client request allows only GZIP compression, and at least one file is in a format not supported by GZIP, ALB will not compress any files.
   Add HTTP Header	You can select the following options: Add X-Forwarded-For to preserve client IP addresses: Add the X-Forwarded-For header to preserve the client IP address If you select Add X-Forwarded-For to preserve client IP addresses, ALB can add an X-Forwarded-For header to or remove the X-Forwarded-For header from the request before forwarding the request to a backend server. Add (default) If you choose Add, ALB adds the IP address of the last hop to the X-Forwarded-For header in the request before forwarding the request to a backend server. If the request does not contain the X-Forwarded-For header, ALB creates an X-Forwarded-For header whose value is the IP address of the last hop and adds the header to the request. The X-Forwarded-For header in the request may contain multiple IP addresses which are separated by commas (,). Remove If you choose Remove, ALB removes the X-Forwarded-For header from the request before forwarding the request to a backend server. If you do not select Add X-Forwarded-For to preserve client IP addresses, ALB does nothing about the X-Forwarded-For header in the request before forwarding the request to a backend server. Format: X-Forwarded-For: <client-ip-address>, <proxy1>, <proxy2>, … Click to see an example about the X-Forwarded-For header in the request that is received by the backend server. In this example, the IP address of the last hop is 127.0.0.1. Request description Sample request Select Add X-Forwarded-For to preserve client IP addresses Not select Add X-Forwarded-For to preserve client IP addresses Add Remove The request received by ALB does not contain the X-Forwarded-For header. GET /index.html HTTP/1.1 Host: example.com X-Forwarded-For: 127.0.0.1 The X-Forwarded-For header does not exist. The X-Forwarded-For header does not exist. The request received by ALB contains the X-Forwarded-For header and a client IP address. GET /index.html HTTP/1.1 Host: example.com X-Forwarded-For: 127.0.0.2 X-Forwarded-For: 127.0.0.2, 127.0.0.1 The X-Forwarded-For header does not exist. X-Forwarded-For: 127.0.0.2 The request received by ALB contains the X-Forwarded-For header and multiple client IP addresses. GET /index.html HTTP/1.1 Host: example.com X-Forwarded-For: 127.0.0.2, 127.0.0.3 X-Forwarded-For: 127.0.0.2, 127.0.0.3, 127.0.0.1 The X-Forwarded-For header does not exist. X-Forwarded-For: 127.0.0.2, 127.0.0.3 For more information about how to enable ALB to preserve client IP addresses, see Obtain client originating IP addresses on backend servers through an Application Load Balancer. Add SLB-ID to preserve SLB instance IDs: Add the SLB-ID header to preserve the ID of the ALB instance. Add X-Forwarded-Proto to preserve listener protocols: Add the X-Forwarded-Proto header to preserve the listener protocol. Add X-Forwarded-Port to preserve SLB listener ports: Add the X-Forwarded-Port header to preserve the listener port. Add X-Forwarded-Host to preserve client domain names: Add the X-Forwarded-Host header to preserve the domain name of a client that accesses ALB. Note Only upgraded ALB instances support adding the X-Forwarded-For and X-Forwarded-Client-srcport headers when you create a QUIC listener.

Step 2: Add an SSL certificate

Configure an SSL certificate to ensure that data transmission is encrypted and the identities of users are verified by a trusted authority. For more information, see Certificate Management Service.

In the Configure SSL Certificate step, select a server certificate or click Create SSL Certificate in the Server Certificate drop-down list to purchase a new certificate. Click Next.

If no server certificate is available, click Create SSL Certificate to create one. For more information, see Purchase an SSL certificate and Upload an SSL certificate.

Step 3: Select a server group

In the Select Server Group step, select a server group, view the backend servers, and then click Next.

Step 4: Review the configuration

In the Configuration Review step, confirm the configurations and click Submit.