AWS prescriptive-guidance documentation change
Summary
Replaced 'Elastic Load Balancing service' with 'ELB service' for terminology consistency
Security assessment
The change is purely terminological, replacing the full service name with its acronym. No security concepts were added, modified, or referenced in the altered text.
Diff
diff --git a/prescriptive-guidance/latest/load-balancer-stickiness/subnets-routing.md b/prescriptive-guidance/latest/load-balancer-stickiness/subnets-routing.md index dceb9bebf..4177818b5 100644 --- a//prescriptive-guidance/latest/load-balancer-stickiness/subnets-routing.md +++ b//prescriptive-guidance/latest/load-balancer-stickiness/subnets-routing.md @@ -21 +21 @@ 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 ELB service and aren't visible to users.) @@ -53 +53 @@ 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 ELB 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. @@ -55 +55 @@ 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 ELB service and aren't visible to users.)