AWS Security ChangesHomeSearch

AWS elasticloadbalancing: Clarify ALB TLS certificate matching and SNI selection behavior

Service: elasticloadbalancing · 2026-10-02 · Documentation medium

File: elasticloadbalancing/latest/application/https-listener-certificates.md · Type: encryption

Summary

Rewrites guidance to explain that the certificate domain must match the client-requested host name for TLS validation, that the load balancer does not serve traffic unencrypted, and that SNI selection uses CN/SAN matching with no fallback to the default certificate.

Security assessment

The change documents TLS certificate validation and SNI certificate-selection semantics for ALB HTTPS listeners, clarifying that connections fail rather than downgrade to unencrypted traffic, which is security-relevant encryption guidance.

Evidence

+If you specify additional certificates in a certificate list, the default certificate is used only if a client connects without using the Server Name Indication (SNI) extension to specify a hostname or if there are no certificates in the certificate list whose CN or SAN matches that hostname. When one or more match, the load balancer selects only from those matched certificates. If none of the matched certificates is compatible with the client, the handshake fails. The load balancer does not fall back to the default certificate.

Diff

diff --git a/elasticloadbalancing/latest/application/https-listener-certificates.md b/elasticloadbalancing/latest/application/https-listener-certificates.md
index 99f1bcc..198f3be 100644
--- a//elasticloadbalancing/latest/application/https-listener-certificates.md
+++ b//elasticloadbalancing/latest/application/https-listener-certificates.md
@@ -13 +13 @@ When you create a secure listener for your Application Load Balancer, you must d
-When you create a certificate for use with your load balancer, you must specify a domain name. The domain name on the certificate must match the custom domain name record so that we can verify the TLS connection. If they do not match, the traffic is not encrypted.
+When you create a certificate for use with your load balancer, you must specify a domain name. The domain name on the certificate must match the host name the client requests so that the client can verify the certificate during the TLS handshake. If they do not match, the client cannot validate the certificate and the connection fails. The load balancer does not serve the traffic unencrypted.
@@ -25 +25 @@ When you create an HTTPS listener, you must specify exactly one certificate. Thi
-If you specify additional certificates in a certificate list, the default certificate is used only if a client connects without using the Server Name Indication (SNI) protocol to specify a hostname or if there are no matching certificates in the certificate list.
+If you specify additional certificates in a certificate list, the default certificate is used only if a client connects without using the Server Name Indication (SNI) extension to specify a hostname or if there are no certificates in the certificate list whose CN or SAN matches that hostname. When one or more match, the load balancer selects only from those matched certificates. If none of the matched certificates is compatible with the client, the handshake fails. The load balancer does not fall back to the default certificate.
@@ -32,0 +33,4 @@ After you create an HTTPS listener, you can add certificates to the certificate
+###### Note
+
+A default certificate takes part in SNI selection only if it is explicitly added to this certificate list using the [AddListenerCertificates](https://docs.aws.amazon.com/elasticloadbalancing/latest/APIReference/API_AddListenerCertificates.html) API. Otherwise, it is used as described in the Default certificate section.
+