SAA-C03 Practice Question 3: S3 Gateway VPC Endpoint
AWS Certified Solutions Architect – Associate (SAA-C03) · Test 1 · question 3 of 10
EC2 instances in the private subnets of a VPC write roughly 8 TB of logs per month to an S3 bucket in the same Region. That traffic currently exits through a NAT gateway, and the NAT gateway's data-processing charges have become the largest line item on the VPC bill.
A new standard requires that traffic from the VPC to Amazon S3 reach the service without an internet gateway or a NAT device. Which change satisfies the standard at the lowest cost?
Show answer and explanation
Answer:
A gateway VPC endpoint gives a VPC reliable connectivity to Amazon S3 and DynamoDB without an internet gateway or a NAT device. When you create it you select route tables, and AWS adds a route whose destination is the service's AWS-managed prefix list and whose target is the endpoint. Every instance in a subnet associated with one of those route tables then reaches S3 over the endpoint. Crucially for the cost requirement, there is no additional charge for gateway endpoints; the 8 TB stops flowing through the NAT gateway and stops being billed for data processing.
Option B does keep the traffic off the internet gateway and NAT device, so it satisfies the standard, but it is the expensive way to do it. Interface endpoints are billed per endpoint per Availability Zone per hour and per GB of data processed, so at 8 TB a month across multiple AZs they cost substantially more than the free gateway endpoint. Interface endpoints for S3 earn their keep when you need to reach the bucket from on-premises over Direct Connect or VPN, something a gateway endpoint cannot do, which is not a requirement here.
Option C removes the NAT charge but fails the standard: instances in a public subnet reach S3 through the internet gateway, and giving log-writing workers public IP addresses makes them reachable from the internet, which is a clear security regression.
Option D changes nothing architecturally. A NAT instance still routes to an internet gateway, so the standard is still violated, and you have swapped a managed, horizontally scaled service for a single EC2 instance that is both a bandwidth bottleneck at 8 TB/month and a single point of failure.
Reference: Gateway endpoints