AWS elasticloadbalancing documentation change
Summary
Replaced 'ELB' with 'Elastic Load Balancing' in the introductory paragraph
Security assessment
Change is a branding update without technical modifications. SSL/TLS security policies, certificate requirements, and authentication mechanisms described remain identical. No evidence of security vulnerability remediation.
Diff
diff --git a/elasticloadbalancing/latest/classic/elb-https-load-balancers.md b/elasticloadbalancing/latest/classic/elb-https-load-balancers.md index e3f68f170..4075a5f16 100644 --- a//elasticloadbalancing/latest/classic/elb-https-load-balancers.md +++ b//elasticloadbalancing/latest/classic/elb-https-load-balancers.md @@ -9 +9 @@ You can create a load balancer that uses the SSL/TLS protocol for encrypted conn -ELB uses Secure Sockets Layer (SSL) negotiation configurations, known as _security policies_ , to negotiate connections between the clients and the load balancer. When you use HTTPS/SSL for your front-end connections, you can use either a predefined security policy or a custom security policy. You must deploy an SSL certificate on your load balancer. The load balancer uses this certificate to terminate the connection and then decrypt requests from clients before sending them to the instances. The load balancer uses a static cipher suite for back-end connections. You can optionally choose to enable authentication on your instances. +Elastic Load Balancing uses Secure Sockets Layer (SSL) negotiation configurations, known as _security policies_ , to negotiate connections between the clients and the load balancer. When you use HTTPS/SSL for your front-end connections, you can use either a predefined security policy or a custom security policy. You must deploy an SSL certificate on your load balancer. The load balancer uses this certificate to terminate the connection and then decrypt requests from clients before sending them to the instances. The load balancer uses a static cipher suite for back-end connections. You can optionally choose to enable authentication on your instances.