AWS vpc documentation change
Summary
Clarified NAT gateway security properties and connection initiation requirements
Security assessment
Reinforces security best practices by emphasizing unsolicited connection prevention, but doesn't address a specific vulnerability
Diff
diff --git a/vpc/latest/userguide/vpc-nat-gateway.md b/vpc/latest/userguide/vpc-nat-gateway.md index 4b149a1d1..3200e9a0f 100644 --- a//vpc/latest/userguide/vpc-nat-gateway.md +++ b//vpc/latest/userguide/vpc-nat-gateway.md @@ -11 +11 @@ When you create a NAT gateway, you specify one of the following connectivity typ - * **Public** – (Default) Instances in private subnets can connect to the internet through a public NAT gateway, but can't receive unsolicited inbound connections from the internet. You create a public NAT gateway in a public subnet and must associate an elastic IP address with the NAT gateway at creation. You route traffic from the NAT gateway to the internet gateway for the VPC. Alternatively, you can use a public NAT gateway to connect to other VPCs or your on-premises network. In this case, you route traffic from the NAT gateway through a transit gateway or a virtual private gateway. + * **Public** – (Default) Instances in private subnets can connect to the internet through a public NAT gateway, but the instances can't receive unsolicited inbound connections from the internet. You create a public NAT gateway in a public subnet and must associate an elastic IP address with the NAT gateway at creation. You route traffic from the NAT gateway to the internet gateway for the VPC. Alternatively, you can use a public NAT gateway to connect to other VPCs or your on-premises network. In this case, you route traffic from the NAT gateway through a transit gateway or a virtual private gateway. @@ -13 +13 @@ When you create a NAT gateway, you specify one of the following connectivity typ - * **Private** – Instances in private subnets can connect to other VPCs or your on-premises network through a private NAT gateway. You can route traffic from the NAT gateway through a transit gateway or a virtual private gateway. You can't associate an elastic IP address with a private NAT gateway. You can attach an internet gateway to a VPC with a private NAT gateway, but if you route traffic from the private NAT gateway to the internet gateway, the internet gateway drops the traffic. + * **Private** – Instances in private subnets can connect to other VPCs or your on-premises network through a private NAT gateway, but the instances can't receive unsolicited inbound connections from the internet. You can route traffic from the NAT gateway through a transit gateway or a virtual private gateway. You can't associate an elastic IP address with a private NAT gateway. You can attach an internet gateway to a VPC with a private NAT gateway, but if you route traffic from the private NAT gateway to the internet gateway, the internet gateway drops the traffic. @@ -23,0 +24,2 @@ Both private and public NAT gateways map the source private IPv4 address of the +Connections must always be initiated from within the VPC containing the NAT Gateway. +