An analytics fleet runs on Amazon EC2 instances in private subnets in one Region. Throughout the day the instances move several terabytes of objects to and from an Amazon S3 bucket and also read and write heavily to an Amazon DynamoDB table, both in the same Region. All of this traffic currently leaves the private subnets through a NAT gateway, and the monthly bill is dominated by NAT gateway data processing charges for the S3 and DynamoDB traffic. The team must eliminate the per-gigabyte NAT charge for both the S3 and the DynamoDB traffic while keeping the instances private, and it does not want to add any new per-hour charge. Which two changes meet these requirements? Select TWO.
- ACreate a gateway VPC endpoint for Amazon S3 and add its prefix list to the route tables of the private subnets so S3 traffic stays on the AWS network. Correct
- BAttach an internet gateway and give the instances public IP addresses so the S3 and DynamoDB traffic reaches the public endpoints directly instead of crossing the NAT gateway.
- CCreate a gateway VPC endpoint for Amazon DynamoDB and add its prefix list to the route tables of the private subnets so DynamoDB traffic stays on the AWS network. Correct
- DCreate an interface VPC endpoint powered by AWS PrivateLink for Amazon S3 in each Availability Zone so the S3 traffic resolves to private endpoint network interfaces.
- EReplace the single NAT gateway with one NAT gateway per Availability Zone so the data processing load is spread across more gateways and the charge falls.
Why A is correct: A gateway VPC endpoint routes same-Region S3 traffic off the NAT path at no hourly or per-gigabyte charge, removing the NAT data processing fee for S3.
Why B is wrong: Public IPs would bypass the NAT gateway, but exposing the instances to the internet breaks the requirement to keep them private, so this is wrong.
Why C is correct: DynamoDB is one of only two services with a gateway endpoint, which carries no hourly or per-gigabyte fee and takes the DynamoDB traffic off the chargeable NAT path.
Why D is wrong: An interface endpoint for S3 works but adds a per-hour and per-gigabyte PrivateLink charge, breaking the no-new-per-hour-cost requirement when a free gateway endpoint exists.
Why E is wrong: Adding NAT gateways spreads load but the per-gigabyte data processing rate is charged on every gateway, so total cost does not fall and may rise.