A media company is reviewing the network architecture of its analytics platform in the us-east-1 Region. The architecture consists of a primary processing VPC (VPC A) containing EC2 instances in private subnets, and a data warehouse VPC (VPC B) containing an Amazon Redshift cluster.
The EC2 instances in VPC A perform the following network operations monthly:
- Download of raw datasets from an Amazon S3 bucket located in the us-east-1 Region.
- Upload of cleansed datasets back to the same Amazon S3 bucket.
- Query and load of aggregated results into the Amazon Redshift cluster in VPC B.
- Download of software patches from external public internet repositories.
Currently, VPC A and VPC B are connected via an AWS Transit Gateway. The private subnets in VPC A route all non-VPC traffic () through a NAT Gateway in a public subnet of VPC A.
Which network architecture configuration will meet these requirements while minimizing data transfer and routing costs?
- Configure a Gateway VPC Endpoint for Amazon S3 in VPC A. Establish a VPC Peering connection between VPC A and VPC B, and configure the route tables to route traffic between the two VPCs through the VPC Peering connection. Retain the NAT Gateway in VPC A for external internet traffic.Cevap
- BKeep the existing AWS Transit Gateway connection and the NAT Gateway in VPC A. Route all Amazon S3 traffic through the NAT Gateway and route the database traffic to VPC B through the AWS Transit Gateway.
- CEstablish a VPC Peering connection between VPC A and VPC B to route database traffic. Replace the NAT Gateway in VPC A with an Interface VPC Endpoint for Amazon S3, routing all S3 traffic through the Interface Endpoint, and configure a Network ACL to bypass data processing charges for S3 traffic.
- DConfigure a Gateway VPC Endpoint for Amazon S3 in VPC A. Route database traffic to VPC B over a new AWS Site-to-Site VPN connection established between the two VPCs to avoid Transit Gateway costs, and route external internet traffic through the VPN connection.