AWS elasticloadbalancing documentation change
Summary
Clarified certificate list initialization behavior when creating HTTPS listeners through different methods
Security assessment
The change clarifies certificate management workflow but doesn't introduce or modify security controls. It's a documentation clarification rather than a security-related update.
Diff
diff --git a/elasticloadbalancing/latest/application/https-listener-certificates.md b/elasticloadbalancing/latest/application/https-listener-certificates.md index 2f8308f0b..60b476420 100644 --- a//elasticloadbalancing/latest/application/https-listener-certificates.md +++ b//elasticloadbalancing/latest/application/https-listener-certificates.md @@ -29 +29 @@ If you do not specify additional certificates but need to host multiple secure a -After you create an HTTPS listener, it has a default certificate and an empty certificate list. If you created the listener via AWS Management Console, the default certificate will be added to the certificate list. You can optionally add certificates to the certificate list for the listener. Using a certificate list enables the load balancer to support multiple domains on the same port and provide a different certificate for each domain. For more information, see [Add certificates to the certificate list](./listener-update-certificates.html#add-certificates). +After you create an HTTPS listener, you can add certificates to the certificate list. If you created the listener using the AWS Management Console, we added the default certificate to the certificate list for you. Otherwise, the certificate list is empty. Using a certificate list enables the load balancer to support multiple domains on the same port and provide a different certificate for each domain. For more information, see [Add certificates to the certificate list](./listener-update-certificates.html#add-certificates).