AWS elasticloadbalancing documentation change
Summary
Updated branding by replacing 'ELB' with 'Elastic Load Balancing' in multiple sections. No technical changes to functionality or configuration.
Security assessment
Changes are purely branding/naming updates (e.g., 'ELB' → 'Elastic Load Balancing'). No modifications to security configurations, vulnerabilities, or features. Existing security content about SSL termination, X-Forwarded-For headers, and cipher compliance remains unchanged.
Diff
diff --git a/elasticloadbalancing/latest/classic/elb-listener-config.md b/elasticloadbalancing/latest/classic/elb-listener-config.md index 34559389e..103d79ff9 100644 --- a//elasticloadbalancing/latest/classic/elb-listener-config.md +++ b//elasticloadbalancing/latest/classic/elb-listener-config.md @@ -9 +9 @@ ProtocolsHTTPS/SSL listeners -Before you start using ELB, you must configure one or more _listeners_ for your Classic Load Balancer. A listener is a process that checks for connection requests. It is configured with a protocol and a port for front-end (client to load balancer) connections, and a protocol and a port for back-end (load balancer to back-end instance) connections. +Before you start using Elastic Load Balancing, you must configure one or more _listeners_ for your Classic Load Balancer. A listener is a process that checks for connection requests. It is configured with a protocol and a port for front-end (client to load balancer) connections, and a protocol and a port for back-end (load balancer to back-end instance) connections. @@ -11 +11 @@ Before you start using ELB, you must configure one or more _listeners_ for your -ELB supports the following protocols: +Elastic Load Balancing supports the following protocols: @@ -49 +49 @@ Communication for a typical web application goes through layers of hardware and -When you use ELB, you need a basic understanding of layer 4 and layer 7. Layer 4 is the transport layer that describes the Transmission Control Protocol (TCP) connection between the client and your back-end instance, through the load balancer. Layer 4 is the lowest level that is configurable for your load balancer. Layer 7 is the application layer that describes the use of Hypertext Transfer Protocol (HTTP) and HTTPS (secure HTTP) connections from clients to the load balancer and from the load balancer to your back-end instance. +When you use Elastic Load Balancing, you need a basic understanding of layer 4 and layer 7. Layer 4 is the transport layer that describes the Transmission Control Protocol (TCP) connection between the client and your back-end instance, through the load balancer. Layer 4 is the lowest level that is configurable for your load balancer. Layer 7 is the application layer that describes the use of Hypertext Transfer Protocol (HTTP) and HTTPS (secure HTTP) connections from clients to the load balancer and from the load balancer to your back-end instance. @@ -65 +65 @@ When you use HTTP (layer 7) for both front-end and back-end connections, your lo -For every registered and healthy instance behind an HTTP/HTTPS load balancer, ELB opens and maintains one or more TCP connections. These connections ensure that there is always an established connection ready to receive HTTP/HTTPS requests. +For every registered and healthy instance behind an HTTP/HTTPS load balancer, Elastic Load Balancing opens and maintains one or more TCP connections. These connections ensure that there is always an established connection ready to receive HTTP/HTTPS requests. @@ -67 +67 @@ For every registered and healthy instance behind an HTTP/HTTPS load balancer, EL -The HTTP requests and HTTP responses use header fields to send information about HTTP messages. ELB supports `X-Forwarded-For` headers. Because load balancers intercept traffic between clients and servers, your server access logs contain only the IP address of the load balancer. To see the IP address of the client, use the `X-Forwarded-For` request header. For more information, see [X-Forwarded-For](./x-forwarded-headers.html#x-forwarded-for). +The HTTP requests and HTTP responses use header fields to send information about HTTP messages. Elastic Load Balancing supports `X-Forwarded-For` headers. Because load balancers intercept traffic between clients and servers, your server access logs contain only the IP address of the load balancer. To see the IP address of the client, use the `X-Forwarded-For` request header. For more information, see [X-Forwarded-For](./x-forwarded-headers.html#x-forwarded-for). @@ -85 +85 @@ If you don't want the load balancer to handle the SSL termination (known as _SSL -ELB provides predefined SSL negotiation configurations that are used for SSL negotiation when a connection is established between a client and your load balancer. The SSL negotiation configurations provide compatibility with a broad range of clients and use high-strength cryptographic algorithms called _ciphers_. However, some use cases might require all data on the network to be encrypted and allow only specific ciphers. Some security compliance standards (such as PCI, SOX, and so on) might require a specific set of protocols and ciphers from clients to ensure that the security standards are met. In such cases, you can create a custom SSL negotiation configuration, based on your specific requirements. Your ciphers and protocols should take effect within 30 seconds. For more information, see [SSL negotiation configurations for Classic Load Balancers](./elb-ssl-security-policy.html). +Elastic Load Balancing provides predefined SSL negotiation configurations that are used for SSL negotiation when a connection is established between a client and your load balancer. The SSL negotiation configurations provide compatibility with a broad range of clients and use high-strength cryptographic algorithms called _ciphers_. However, some use cases might require all data on the network to be encrypted and allow only specific ciphers. Some security compliance standards (such as PCI, SOX, and so on) might require a specific set of protocols and ciphers from clients to ensure that the security standards are met. In such cases, you can create a custom SSL negotiation configuration, based on your specific requirements. Your ciphers and protocols should take effect within 30 seconds. For more information, see [SSL negotiation configurations for Classic Load Balancers](./elb-ssl-security-policy.html).