AWS vpc documentation change
Summary
Removed 'AWS' prefix from 'Direct Connect' service name
Security assessment
Change is purely terminological (branding update) with no impact on security concepts. The security posture of requiring gateways for internet access remains unchanged.
Diff
diff --git a/vpc/latest/userguide/vpc-ip-addressing.md b/vpc/latest/userguide/vpc-ip-addressing.md index f6a21b29c..edbc73ab7 100644 --- a//vpc/latest/userguide/vpc-ip-addressing.md +++ b//vpc/latest/userguide/vpc-ip-addressing.md @@ -61 +61 @@ You can assign additional private IP addresses, known as secondary private IP ad -We refer to private IP addresses as the IP addresses that are within the IPv4 CIDR range of the VPC. Most VPC IP address ranges fall within the private (non-publicly routable) IP address ranges specified in RFC 1918; however, you can use publicly routable CIDR blocks for your VPC. Regardless of the IP address range of your VPC, we do not support direct access to the internet from your VPC's CIDR block, including a publicly-routable CIDR block. You must set up internet access through a gateway; for example, an internet gateway, virtual private gateway, a AWS Site-to-Site VPN connection, or AWS Direct Connect. +We refer to private IP addresses as the IP addresses that are within the IPv4 CIDR range of the VPC. Most VPC IP address ranges fall within the private (non-publicly routable) IP address ranges specified in RFC 1918; however, you can use publicly routable CIDR blocks for your VPC. Regardless of the IP address range of your VPC, we do not support direct access to the internet from your VPC's CIDR block, including a publicly-routable CIDR block. You must set up internet access through a gateway; for example, an internet gateway, virtual private gateway, a AWS Site-to-Site VPN connection, or Direct Connect.