AWS elasticloadbalancing documentation change
Summary
Minor wording improvements: clarified ALB scaling behavior, Local Zone subnet support, HTTP/2 functionality, and desync mitigation attributes. No functional changes.
Security assessment
Changes are editorial improvements and clarifications of existing functionality. While HTTP desync mitigation is mentioned, this is existing security documentation rather than new security content. No specific security vulnerability or new security feature is introduced in these changes.
Diff
diff --git a/elasticloadbalancing/latest/application/application-load-balancers.md b/elasticloadbalancing/latest/application/application-load-balancers.md index a6632c535..758b0df0e 100644 --- a//elasticloadbalancing/latest/application/application-load-balancers.md +++ b//elasticloadbalancing/latest/application/application-load-balancers.md @@ -98 +98 @@ You must select at least two Availability Zone subnets. The following restrictio -**Note:** If an Application Load Balancers subnet runs out of usable IP addresses while attempting to scale, the Application Load Balancer will run with insufficient capacity. During this time old nodes will continue to serve traffic, but the stalled scaling attempt may cause 5xx errors or timeouts when attempting to establish a connection. +**Note:** If an Application Load Balancers subnet runs out of usable IP addresses while attempting to scale, the Application Load Balancer will run with insufficient capacity. During this time, old nodes continue to serve traffic, but the stalled scaling attempt might cause 5xx errors or timeouts when attempting to establish a connection. @@ -105 +105 @@ You must select at least two Availability Zone subnets. The following restrictio -You can specify one or more Local Zone subnets. The following features are not supported: +You can specify Local Zone subnets. The following features are not supported with local zone subnets: @@ -276 +276 @@ Enables you to modify, preserve, or remove the `X-Forwarded-For` header in the H -Indicates whether HTTP/2 is enabled. The default is `true`. +Indicates whether clients can connect to the load balancer using HTTP/2. If `true`, clients can connect using HTTP/2 or HTTP/1.1. If `false`, clients must connect using HTTP/1.1. The default is `true`. @@ -285 +285 @@ Indicates whether to allow a AWS WAF-enabled load balancer to route requests to -The `routing.http.drop_invalid_header_fields.enabled` attribute was introduced to offer HTTP desync protection. The `routing.http.desync_mitigation_mode` attribute was added to provide more comprehensive protection from HTTP desync for your applications. You aren't required to use both attributes and may choose either, depending on your application's requirements. +The `routing.http.drop_invalid_header_fields.enabled` attribute was introduced to offer HTTP desync protection. The `routing.http.desync_mitigation_mode` attribute was added to provide more comprehensive protection from HTTP desync for your applications. You aren't required to use both attributes and can choose whichever attribute best meets your application's requirements. @@ -392 +392 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Getting started using the AWS CLI +What is an Application Load Balancer?