AWS Application Load Balancer adds new header for client TLS connection key exchange group

Posted on: Nov 19, 2026

AWS Application Load Balancer (ALB) now supports a new header to convey the TLS key exchange group of the client connection. ALB adds the "x-amzn-tls-kx" request header that captures the TLS key exchange group negotiated between the client and the load balancer. The header tells your applications whether a client connection uses classical or hybrid post-quantum key exchange.

Until now, you had to rely on ALB connection logs to retrieve the negotiated key exchange group. The new header makes it easier for your applications, security information and event management (SIEM) tools, or analytics pipelines to consume this information. On HTTPS listeners, the new header covers TLS 1.2 and TLS 1.3 connections and contains classical groups such as x25519 or secp256r1, or hybrid post-quantum groups such as X25519MLKEM768 on TLS 1.3. You can use the header to measure post-quantum TLS adoption, detect clients that fall back to classical key exchange, and support compliance audits without packet captures.

To get started, set the routing.http.x_amzn_tls_kx.enabled load balancer attribute to true. The attribute is independent of routing.http.x_amzn_tls_version_and_cipher_suite.enabled. This feature is available at no additional cost in all AWS Commercial Regions, the AWS GovCloud (US) Regions, and the China Regions. It is available in the AWS Management Console, AWS CLI, Elastic Load Balancing API, or AWS SDKs. To learn more, see Load balancer attributes in the User Guide for Application Load Balancers or visit the Elastic Load Balancing product page.