A company's SysOps administrator is reviewing the monthly AWS billing report and notices high charges under 'EC2-Other' due to NAT Gateway data processing fees and cross-Availability Zone (cross-AZ) billing. The application architecture consists of EC2 instances hosted in private subnets across three Availability Zones (`us-west-2a`, `us-west-2b`, and `us-west-2c`) within a single VPC in the `us-west-2` Region. These instances upload approximately of data monthly to an Amazon S3 bucket located in the same Region. Currently, the VPC is configured with a single NAT Gateway in `us-west-2a`, and all private subnet route tables direct default outbound traffic () to this NAT Gateway. Which of the following is the most cost-effective solution to eliminate these data transfer charges while keeping the instances within private subnets?
- Create an Amazon S3 Gateway VPC Endpoint, associate it with the route tables of all private subnets across the three Availability Zones, and ensure the S3 bucket policy permits access from the VPC.Cevap
- BDeploy Interface VPC Endpoints (AWS PrivateLink) for Amazon S3 in the private subnets of all three Availability Zones, and update the application configuration to connect via the private endpoint DNS.
- CDeploy a dedicated NAT Gateway in the public subnet of each Availability Zone, and update the private subnet route tables to route outbound traffic through their respective local NAT Gateway.
- DCreate an Amazon S3 Gateway VPC Endpoint and associate it only with the public subnet's route table where the NAT Gateway is deployed, allowing the private subnets to continue using their current default route.