AWS prescriptive-guidance documentation change
Summary
Updated documentation links, corrected punctuation, and modified image paths/references in load balancer traffic flow documentation
Security assessment
Changes consist of typographical corrections (apostrophe formatting), navigation link updates, and image path modifications. No security-related content additions or vulnerability mitigations are mentioned. The updates maintain existing architectural best practices without introducing new security considerations.
Diff
diff --git a/prescriptive-guidance/latest/load-balancer-stickiness/subnets-routing.md b/prescriptive-guidance/latest/load-balancer-stickiness/subnets-routing.md index 8f1fee21a..59615c56d 100644 --- a//prescriptive-guidance/latest/load-balancer-stickiness/subnets-routing.md +++ b//prescriptive-guidance/latest/load-balancer-stickiness/subnets-routing.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) @@ -11 +11 @@ Inbound traffic pathReturn traffic pathComplete traffic flow diagram -Let's start with an illustration of how traffic flows when you configure an [Application Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/introduction.html) that faces the internet, to Amazon Elastic Compute Cloud (Amazon EC2) instances in a private subnet. This architecture reflects best practices when deploying an Application Load Balancer that’s open to the internet. +Let's start with an illustration of how traffic flows when you configure an [Application Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/introduction.html) that faces the internet, to Amazon Elastic Compute Cloud (Amazon EC2) instances in a private subnet. This architecture reflects best practices when deploying an Application Load Balancer that's open to the internet. @@ -17 +17 @@ The following diagram illustrates the virtual private cloud (VPC) subnets and ro - + @@ -21 +21 @@ The following diagram illustrates the virtual private cloud (VPC) subnets and ro - 2. The Application Load Balancer is associated with two public subnets in the scenario that’s illustrated. The Elastic Load Balancing service creates load balancer capacity in each enabled Availability Zone, and sends traffic through the Availability Zone to determine the appropriate routing logic. The Application Load Balancer uses its internal logic to determine which target group and instance to route the traffic to. + 2. The Application Load Balancer is associated with two public subnets in the scenario that's illustrated. The Elastic Load Balancing service creates load balancer capacity in each enabled Availability Zone, and sends traffic through the Availability Zone to determine the appropriate routing logic. The Application Load Balancer uses its internal logic to determine which target group and instance to route the traffic to. @@ -23 +23 @@ The following diagram illustrates the virtual private cloud (VPC) subnets and ro - 3. The Application Load Balancer routes the request to the EC2 instance through a node that’s associated with the public subnet in the same Availability Zone. (These nodes are configured, managed, and scaled by the Elastic Load Balancing service and aren't visible to users.) + 3. The Application Load Balancer routes the request to the EC2 instance through a node that's associated with the public subnet in the same Availability Zone. (These nodes are configured, managed and scaled by the Elastic Load Balancing service and aren't visible to users.) @@ -34 +34 @@ The following diagram illustrates the VPC subnets and routing associated with th - + @@ -51 +51 @@ The following diagram combines the inbound and return traffic flows to provide a - + @@ -55 +55 @@ The following diagram combines the inbound and return traffic flows to provide a - 2. The Application Load Balancer is associated with two public subnets in the scenario that’s illustrated. The Elastic Load Balancing service creates load balancer capacity in each enabled Availability Zone, and sends traffic through the Availability Zone to determine the appropriate routing logic. The Application Load Balancer uses its internal logic to determine which target group and instance to route the traffic to. + 2. The Application Load Balancer is associated with two public subnets in the scenario that's illustrated. The Elastic Load Balancing service creates load balancer capacity in each enabled Availability Zone, and sends traffic through the Availability Zone to determine the appropriate routing logic. The Application Load Balancer uses its internal logic to determine which target group and instance to route the traffic to. @@ -57 +57 @@ The following diagram combines the inbound and return traffic flows to provide a - 3. The Application Load Balancer routes the request to the EC2 instance through a node that’s associated with the public subnet in the same Availability Zone. (These nodes are configured, managed, and scaled by the Elastic Load Balancing service and aren't visible to users.) + 3. The Application Load Balancer routes the request to the EC2 instance through a node that's associated with the public subnet in the same Availability Zone. (These nodes are configured, managed, and scaled by the Elastic Load Balancing service and aren't visible to users.)