A company has a multi-VPC architecture in the `eu-west-1` Region. VPC A contains a fleet of Amazon EC2 instances running in private subnets that process and upload of data monthly to an Amazon S3 bucket in the same Region. VPC A is connected to a central egress VPC via an AWS Transit Gateway. Currently, all outbound traffic from VPC A, including S3 traffic, is routed through the Transit Gateway to the egress VPC, which routes the traffic to the internet through a pair of NAT Gateways. This architecture has resulted in very high data transfer and processing charges. A solutions architect must implement a solution to minimize these costs.
Which solution is the most cost-effective?
- Create an Amazon S3 Gateway VPC Endpoint in VPC A. Update the route tables of the private subnets in VPC A to direct traffic destined for S3 to the S3 Gateway VPC Endpoint.Cevap
- BCreate an Amazon S3 Gateway VPC Endpoint in the central egress VPC. Configure the Transit Gateway route tables to route all S3-destined traffic from VPC A to the central egress VPC's endpoint.
- CCreate Amazon S3 Interface VPC Endpoints (AWS PrivateLink) in the private subnets of VPC A. Configure the EC2 instances to route S3 traffic through these interface endpoints.
- DPurchase Compute Savings Plans to cover the data processing and transfer charges of the Transit Gateway and the NAT Gateways in the central egress VPC.
Cevap
Create an Amazon S3 Gateway VPC Endpoint in VPC A and update the route tables of the private subnets in VPC A to direct S3 traffic to it.
Creating a Gateway VPC Endpoint for Amazon S3 directly in VPC A is the most cost-effective solution. Gateway VPC Endpoints are offered at no cost (no hourly or data processing fees). By directing S3 traffic through the gateway endpoint locally in VPC A, the traffic bypasses both the Transit Gateway and the central NAT Gateways, completely eliminating the associated processing charges for the of S3 data transfer.
Adım Adım Çözüm
Anahtar Kavram
Using Gateway VPC Endpoints to optimize data transfer costs for Amazon S3 traffic within the same AWS Region while respecting transitive routing limitations.