AWS vpc documentation change
Summary
Replaced 'Elastic Load Balancing' with 'ELB' abbreviation in network ACL documentation.
Security assessment
Changes are purely terminological (abbreviating service names). No modifications to security policies, vulnerabilities, or security-related content were made.
Diff
diff --git a/vpc/latest/userguide/custom-network-acl.md b/vpc/latest/userguide/custom-network-acl.md index 05a7a7e94..cf50cc55b 100644 --- a//vpc/latest/userguide/custom-network-acl.md +++ b//vpc/latest/userguide/custom-network-acl.md @@ -59 +59 @@ The client that initiates the request chooses the ephemeral port range. The rang - * Requests originating from Elastic Load Balancing use ports 1024-65535. + * Requests originating from ELB use ports 1024-65535. @@ -82 +82 @@ If you create a custom network ACL, be aware of how it might affect resources th -With Elastic Load Balancing, if the subnet for your backend instances has a network ACL in which you've added a _deny_ rule for all traffic with a source of either `0.0.0.0/0` or the subnet's CIDR, your load balancer can't carry out health checks on the instances. For more information about the recommended network ACL rules for your load balancers and backend instances, see the following: +With ELB, if the subnet for your backend instances has a network ACL in which you've added a _deny_ rule for all traffic with a source of either `0.0.0.0/0` or the subnet's CIDR, your load balancer can't carry out health checks on the instances. For more information about the recommended network ACL rules for your load balancers and backend instances, see the following: