AWS elasticbeanstalk documentation change
Summary
Updated explanation about Network Load Balancer listeners to mention TLS listener option
Security assessment
Added reference to TLS listener configuration which handles encryption at load balancer level. This improves documentation of security features but doesn't address a specific vulnerability.
Diff
diff --git a/elasticbeanstalk/latest/dg/configuring-https-endtoend.md b/elasticbeanstalk/latest/dg/configuring-https-endtoend.md index 1b5b1f4b0..5e830af1f 100644 --- a//elasticbeanstalk/latest/dg/configuring-https-endtoend.md +++ b//elasticbeanstalk/latest/dg/configuring-https-endtoend.md @@ -59 +59 @@ The `DefaultProcess` option is named this way because of Application Load Balanc -In this example, we named the process `https` because it listens to secure (HTTPS) traffic. The listener sends traffic to the process on the designated port using the TCP protocol, because a Network Load Balancer works only with TCP. This is okay, because network traffic for HTTP and HTTPS is implemented on top of TCP. +In this example, we named the process `https` because it listens to secure (HTTPS) traffic. The listener sends traffic to the process on the designated port using the TCP protocol. You can also configure a TLS listener on your Network Load Balancer to handle the secure connection at the load balancer. For more information, see [Network Load Balancer](./environments-cfg-nlb.html).