AWS elasticloadbalancing documentation change
Summary
Minor wording changes: replaced 'use' with 'utilize', 'to provide' with 'in order to provide', and 'before' with 'prior to'.
Security assessment
Changes are purely editorial with no security implications. No vulnerabilities, configurations, or security features are modified or documented.
Diff
diff --git a/elasticloadbalancing/latest/application/edit-target-group-attributes.md b/elasticloadbalancing/latest/application/edit-target-group-attributes.md index 051f59935..3a9034bfc 100644 --- a//elasticloadbalancing/latest/application/edit-target-group-attributes.md +++ b//elasticloadbalancing/latest/application/edit-target-group-attributes.md @@ -360 +360 @@ With Application Load Balancers, cross-zone load balancing is always turned on a - * Plan for enough target capacity across all Availability Zones that you expect to use, per target group. If you can't plan for enough capacity across all participating Availability Zones, we recommend that you keep cross-zone load balancing on. + * Plan for enough target capacity across all Availability Zones that you expect to utilize, per target group. If you can't plan for enough capacity across all participating Availability Zones, we recommend that you keep cross-zone load balancing on. @@ -654 +654 @@ Use the [describe-target-health](https://docs.aws.amazon.com/cli/latest/referenc -By default, an Application Load Balancer routes each request independently to a registered target based on the chosen load-balancing algorithm. However, you can use the sticky session feature (also known as session affinity) to enable the load balancer to bind a user's session to a specific target. This ensures that all requests from the user during the session are sent to the same target. This feature is useful for servers that maintain state information to provide a continuous experience to clients. To use sticky sessions, the client must support cookies. +By default, an Application Load Balancer routes each request independently to a registered target based on the chosen load-balancing algorithm. However, you can use the sticky session feature (also known as session affinity) to enable the load balancer to bind a user's session to a specific target. This ensures that all requests from the user during the session are sent to the same target. This feature is useful for servers that maintain state information in order to provide a continuous experience to clients. To use sticky sessions, the client must support cookies. @@ -897 +897 @@ When scaling up, if the number of targets increase considerably, there is potent - * Set an expiry on the cookie generated by the application that is before the current date and time. This prevents clients from sending the cookie to the Application Load Balancer, which will restart the process of establishing stickiness. + * Set an expiry on the cookie generated by the application that is prior to the current date and time. This prevents clients from sending the cookie to the Application Load Balancer, which will restart the process of establishing stickiness.