AWS elasticloadbalancing documentation change
Summary
Updated terminology from 'Elastic Load Balancing' to 'ELB' abbreviation and changed 'AWS VPN' to 'Site-to-Site VPN' in multiple sections for consistency
Security assessment
The changes are primarily terminology updates (abbreviations and VPN service name standardization). While some sections mention security-related concepts like blocking internet gateway access and HTTP header validation, these are existing security controls being described with updated terminology rather than new security content.
Diff
diff --git a/elasticloadbalancing/latest/application/application-load-balancers.md b/elasticloadbalancing/latest/application/application-load-balancers.md index 24391ab08..8a6cbd4f0 100644 --- a//elasticloadbalancing/latest/application/application-load-balancers.md +++ b//elasticloadbalancing/latest/application/application-load-balancers.md @@ -11 +11 @@ A _load balancer_ serves as the single point of contact for clients. Clients sen -For more information, see [How Elastic Load Balancing works](https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/how-elastic-load-balancing-works.html) in the _Elastic Load Balancing User Guide_. +For more information, see [How ELB works](https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/how-elastic-load-balancing-works.html) in the _Elastic Load Balancing User Guide_. @@ -62 +62 @@ For more information, see [How Elastic Load Balancing works](https://docs.aws.am -When you create an Application Load Balancer, you must enable the zones that contain your targets. To enable a zone, specify a subnet in the zone. Elastic Load Balancing creates a load balancer node in each zone that you specify. +When you create an Application Load Balancer, you must enable the zones that contain your targets. To enable a zone, specify a subnet in the zone. ELB creates a load balancer node in each zone that you specify. @@ -74 +74 @@ When you create an Application Load Balancer, you must enable the zones that con - * Elastic Load Balancing creates network interfaces in the subnets where you configured your load balancer. These network interfaces are reserved so that the load balancer can complete maintenance actions even when the subnet is running low on available IP addresses. They have the description "ENI reserved by ELB for subnet". + * ELB creates network interfaces in the subnets where you configured your load balancer. These network interfaces are reserved so that the load balancer can complete maintenance actions even when the subnet is running low on available IP addresses. They have the description "ENI reserved by ELB for subnet". @@ -234 +234 @@ The idle timeout value, in seconds. The default is 60 seconds. -Blocks internet gateway (IGW) access to the load balancer, preventing unintended access to your internal load balancer through an internet gateway. It is set to `false` for internet-facing load balancers and `true` for internal load balancers. This attribute does not prevent non-IGW internet access (such as, through peering, Transit Gateway, AWS Direct Connect, or AWS VPN). +Blocks internet gateway (IGW) access to the load balancer, preventing unintended access to your internal load balancer through an internet gateway. It is set to `false` for internet-facing load balancers and `true` for internal load balancers. This attribute does not prevent non-IGW internet access (such as, through peering, Transit Gateway, AWS Direct Connect, or Site-to-Site VPN). @@ -244 +244 @@ Determines how the load balancer handles requests that might pose a security ris -Indicates whether HTTP headers with header fields that are not valid are removed by the load balancer (`true`), or routed to targets (`false`). The default is `false`. Elastic Load Balancing requires that valid HTTP header names conform to the regular expression `[-A-Za-z0-9]+`, as described in the HTTP Field Name Registry. Each name consists of alphanumeric characters or hyphens. Select `true` if you want HTTP headers that do not conform to this pattern, to be removed from requests. +Indicates whether HTTP headers with header fields that are not valid are removed by the load balancer (`true`), or routed to targets (`false`). The default is `false`. ELB requires that valid HTTP header names conform to the regular expression `[-A-Za-z0-9]+`, as described in the HTTP Field Name Registry. Each name consists of alphanumeric characters or hyphens. Select `true` if you want HTTP headers that do not conform to this pattern, to be removed from requests. @@ -314 +314 @@ Clients must connect to the load balancer using IPv6 addresses (for example, 200 - * When you enable dualstack mode for the load balancer, Elastic Load Balancing provides an AAAA DNS record for the load balancer. Clients that communicate with the load balancer using IPv4 addresses resolve the A DNS record. Clients that communicate with the load balancer using IPv6 addresses resolve the AAAA DNS record. + * When you enable dualstack mode for the load balancer, ELB provides an AAAA DNS record for the load balancer. Clients that communicate with the load balancer using IPv4 addresses resolve the A DNS record. Clients that communicate with the load balancer using IPv6 addresses resolve the AAAA DNS record. @@ -316 +316 @@ Clients must connect to the load balancer using IPv6 addresses (for example, 200 - * Access to your internal dualstack load balancers through the internet gateway is blocked to prevent unintended internet access. However, this does not prevent non-IGW internet access (such as, through peering, Transit Gateway, AWS Direct Connect, or AWS VPN). + * Access to your internal dualstack load balancers through the internet gateway is blocked to prevent unintended internet access. However, this does not prevent non-IGW internet access (such as, through peering, Transit Gateway, AWS Direct Connect, or Site-to-Site VPN). @@ -345 +345 @@ To get started, create an IPAM IP address pool. For more information, see [Bring -If there are no more assignable IP addresses in your IPAM IP address pool, Elastic Load Balancing uses AWS managed IPv4 addresses instead. There are additional charges to use AWS managed IPv4 addresses. To avoid these costs, you can add IP address ranges to your existing IPAM IP address pool. +If there are no more assignable IP addresses in your IPAM IP address pool, ELB uses AWS managed IPv4 addresses instead. There are additional charges to use AWS managed IPv4 addresses. To avoid these costs, you can add IP address ranges to your existing IPAM IP address pool.