A SysOps Administrator creates a Gateway VPC Endpoint for Amazon S3 in a VPC. However, EC2 instances in a private subnet continue to access Amazon S3 through a NAT Gateway, resulting in high NAT Gateway data processing charges. Which configuration issue is the root cause of this behavior?
- AThe private subnet's route table is missing a route targeting the Internet Gateway for the S3 prefix list.
- The Gateway VPC Endpoint was not associated with the route table of the private subnet.Answer
- CThe private subnet's route table directs S3 traffic to the NAT Gateway in the public subnet instead of the VPC Endpoint's network interface.
- DThe Network Access Control List (NACL) associated with the private subnet is blocking outbound ephemeral ports to S3.
Answer
The Gateway VPC Endpoint was not associated with the route table of the private subnet.
The correct answer is that the Gateway VPC Endpoint was not associated with the route table of the private subnet. For Gateway VPC Endpoints, AWS automatically updates the associated route tables with a prefix list route pointing to the endpoint. If the route table is not associated, traffic destined for Amazon S3 falls back to the default route, which in this case points to the NAT Gateway.
Step-by-Step Solution
Key Concept
Gateway VPC Endpoints must be associated with subnet route tables to redirect traffic privately without using a NAT Gateway.