AWS prescriptive-guidance documentation change
Summary
Updated documentation links, formatting, and terminology (e.g., 'EC2' to 'Amazon EC2'). Consolidated notes section and fixed punctuation/formatting.
Security assessment
Changes are editorial improvements (link updates, terminology standardization, punctuation fixes). No security vulnerabilities, configurations, or features are introduced or modified. The note about NAT gateway costs and EC2 instance usage relates to cost optimization rather than security.
Diff
diff --git a/prescriptive-guidance/latest/load-balancer-stickiness/alb-without-stickiness.md b/prescriptive-guidance/latest/load-balancer-stickiness/alb-without-stickiness.md index 616c03a0f..0a9b7d5aa 100644 --- a//prescriptive-guidance/latest/load-balancer-stickiness/alb-without-stickiness.md +++ b//prescriptive-guidance/latest/load-balancer-stickiness/alb-without-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) @@ -13 +13 @@ When you use an Application Load Balancer without any form of stickiness, by def -**Template:** Use the CloudFormation template `basic.yml` (included in the [sample code .zip file](samples/stickiness.zip)) to try out this functionality. +**Template** : Use the CloudFormation template `basic.yml` (included in the attached .zip file) to try out this functionality. @@ -17 +17 @@ When you use an Application Load Balancer without any form of stickiness, by def -All CloudFormation templates included with this guide deploy a custom VPC, route tables, routes, an internet gateway, an Application Load Balancer, target groups, listeners, and EC2 instances, to illustrate a specific load balancer stickiness strategy. +All CloudFormation templates included with this guide deploy a custom VPC, route tables, routes, an internet gateway, an Application Load Balancer, target groups, listeners, and Amazon EC2 instances, to illustrate a specific load balancer stickiness strategy. @@ -25 +25 @@ Use an Application Load Balancer without stickiness in these scenarios: - * You’re using web servers that do not maintain session state. + * You're using web servers that do not maintain session state. @@ -27 +27 @@ Use an Application Load Balancer without stickiness in these scenarios: - * You’re using application servers that do not maintain session state. + * You're using application servers that do not maintain session state. @@ -34,7 +34 @@ Use an Application Load Balancer without stickiness in these scenarios: -###### Notes - - * NAT gateways incur a small cost. - - * Multiple EC2 instances use up your free tier hours faster than a single EC2 instance. - - +###### Note @@ -41,0 +36 @@ Use an Application Load Balancer without stickiness in these scenarios: +NAT gateways incur a small cost, and multiple Amazon EC2 instances use up your free tier hours faster than a single instance. @@ -60 +55 @@ The webpage displays **Instance 1 - TG1** or **Instance 2 - TG1**. -The instance that loads the web page (**Instance 1** or **Instance 2**) should change every time, as reflected in the page text. The load balancer logic manages the last target across multiple internal nodes, which may introduce a synchronization delay, so there’s a possibility that you will be routed to the same target. +The instance that loads the web page (Instance 1 or Instance 2) should change every time, as reflected in the page text. The load balancer logic manages the last target across multiple internal nodes, which may introduce a synchronization delay, so there's a possibility that you will be routed to the same target.