A fleet of application servers resides in a private subnet within Spoke VPC A. The servers regularly write large analytics payloads to an Amazon DynamoDB table in the same AWS Region. The network topology utilizes a hub-and-spoke model where Spoke VPC A is connected to a central Hub VPC via an AWS Transit Gateway, and all internet-bound traffic is routed through a centralized NAT Gateway in the Hub VPC. The SysOps administrator identifies that this DynamoDB write traffic is incurring both Transit Gateway and NAT Gateway data processing charges, significantly inflating the monthly bill. Which configuration will eliminate the data processing charges for this traffic in the most cost-effective manner?
- Create a Gateway VPC endpoint for DynamoDB in Spoke VPC A, and select the private subnet's route table during creation to automatically add the route.Answer
- BDeploy an Interface VPC endpoint (AWS PrivateLink) for DynamoDB in Spoke VPC A, and update the private subnet's route table to route DynamoDB traffic to the endpoint network interface.
- CCreate a Gateway VPC endpoint for DynamoDB in Spoke VPC A, but do not associate it with any route tables, and instead add a manual route pointing to the endpoint's Elastic Network Interface (ENI).
- DDeploy a local NAT Gateway in a public subnet within Spoke VPC A, and update the private subnet's route table to direct DynamoDB traffic through the local NAT Gateway.
Answer
Create a Gateway VPC endpoint for DynamoDB in Spoke VPC A, and select the private subnet's route table during creation to automatically add the route.
The correct option is to create a Gateway VPC endpoint and associate it with the private subnet's route table. Gateway endpoints are free and route DynamoDB traffic privately, avoiding the processing charges of both the Transit Gateway and the NAT Gateway.
Step-by-Step Solution
Key Concept
Gateway VPC endpoints provide free, direct private connectivity to DynamoDB and S3, bypassing NAT Gateways and Transit Gateways to eliminate processing fees.