AWS wellarchitected documentation change
Summary
Changed 'ELB' to 'Elastic Load Balancing' in public endpoint recommendations
Security assessment
Terminology clarification without security impact. Network protection strategy and layered security approach remain identical.
Diff
diff --git a/wellarchitected/2025-02-25/framework/sec_network_protection_create_layers.md b/wellarchitected/2025-02-25/framework/sec_network_protection_create_layers.md index bd3905eb3..de07a9b7f 100644 --- a//wellarchitected/2025-02-25/framework/sec_network_protection_create_layers.md +++ b//wellarchitected/2025-02-25/framework/sec_network_protection_create_layers.md @@ -42 +42 @@ As part of your design, consider how using AWS managed services influences your - 2. For components responding to requests from the internet, consider using load balancers or other proxies to provide public endpoints. Explore shifting security controls by using managed services, such as CloudFront, [Amazon API Gateway](https://aws.amazon.com/api-gateway/), ELB, and [AWS Amplify](https://aws.amazon.com/amplify/) to host public endpoints. + 2. For components responding to requests from the internet, consider using load balancers or other proxies to provide public endpoints. Explore shifting security controls by using managed services, such as CloudFront, [Amazon API Gateway](https://aws.amazon.com/api-gateway/), Elastic Load Balancing, and [AWS Amplify](https://aws.amazon.com/amplify/) to host public endpoints.