AWS wellarchitected documentation change
Summary
Updated 'ELB' to 'Elastic Load Balancing' in managed services list for public endpoints
Security assessment
Cosmetic naming update. Security controls for public endpoints remain unchanged. No modification to security properties of load balancers or threat mitigation guidance.
Diff
diff --git a/wellarchitected/latest/security-pillar/sec_network_protection_create_layers.md b/wellarchitected/latest/security-pillar/sec_network_protection_create_layers.md index 7953273fa..f4b1f7256 100644 --- a//wellarchitected/latest/security-pillar/sec_network_protection_create_layers.md +++ b//wellarchitected/latest/security-pillar/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.