AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb links, fixed template references, consolidated notes about costs, corrected instance display text, and fixed typos in stickiness behavior explanation.
Security assessment
Changes involve documentation formatting, link corrections, and content clarifications. No security vulnerabilities, patches, or security-specific features are mentioned. The typo fix ('a a binding') doesn't address a security flaw but improves readability.
Diff
diff --git a/prescriptive-guidance/latest/load-balancer-stickiness/target-group-stickiness.md b/prescriptive-guidance/latest/load-balancer-stickiness/target-group-stickiness.md index 5c1970849..5347676cb 100644 --- a//prescriptive-guidance/latest/load-balancer-stickiness/target-group-stickiness.md +++ b//prescriptive-guidance/latest/load-balancer-stickiness/target-group-stickiness.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Choosing a stickiness strategy for your load balancer](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Choosing a stickiness strategy for your load balancer](introduction.html) @@ -20 +20 @@ When you use an Application Load Balancer with target group stickiness: -**Template:** Use the CloudFormation template `targetgroupstickiness.yml` (included in the [sample code .zip file](samples/stickiness.zip)) to try out target group stickiness. +**Template** : Use the CloudFormation template `targetgroupstickiness.yml` (included in the attached .zip file) to try out target group stickiness. @@ -35 +35 @@ Use target group stickiness in these scenarios: -A single change has been made to the listener: We modified the Application Load Balancer default actions to specify two target groups (`TG1` and `TG2`) of equal weight, with a stickiness configuration. +A single change has been made to the listener: We modified the Application Load Balancer default actions to specify two target groups (TG1 and TG2) of equal weight, with a stickiness configuration. @@ -37 +37 @@ A single change has been made to the listener: We modified the Application Load -**`basic.yml`** | **`targetgroupstickiness.yml`** +`basic.yml`| `targetgroupstickiness.yml` @@ -74,7 +74 @@ A single change has been made to the listener: We modified the Application Load -###### Notes - - * NAT gateways incur a small cost. - - * Multiple EC2 instances use up your free tier hours faster than a single EC2 instance. - - +###### Note @@ -81,0 +76 @@ A single change has been made to the listener: We modified the Application Load +NAT gateways incur a small cost, and multiple Amazon EC2 instances use up your free tier hours faster than a single instance. @@ -91 +86 @@ For example: `http://alb-123456789.us-east-1.elb.amazonaws.com/` -The webpage displays one of the following: **Instance 1 - TG1** , **Instance 2 - TG1** , **Instance 3 - TG2** , or **Instance 4 - TG2**. +The webpage displays one of the following: **Instance 1 - TG1,** **Instance 2 - TG1** , **Instance 3 - TG2,** or **Instance 4 - TG1**. @@ -112 +107 @@ After approximately 10 seconds, the stickiness is released and the target group - * The Application Load Balancer creates a binding for the user's session toward the destination target group, with an expiration time. + * The Application Load Balancer creates a a binding for the user's session toward the destination target group, with an expiration time. @@ -116 +111 @@ After approximately 10 seconds, the stickiness is released and the target group - * If the binding has expired or doesn’t exist, the Application Load Balancer runs its routing logic and determines the destination target group. + * If the binding has expired or doesn't exist, the Application Load Balancer runs its routing logic and determines the destination target group.