An enterprise runs a large-scale data analytics platform on AWS. The central data lake is hosted in an Amazon S3 bucket in the `us-west-2` Region, containing of data that changes or grows by approximately each month. A processing cluster runs on Amazon EKS nodes located in private subnets across Availability Zones in the `us-east-1` Region. The cluster executes batch analysis jobs every day, reading a total of of data monthly from the `us-west-2` bucket. Currently, the EKS nodes access the S3 bucket via local NAT Gateways in each Availability Zone. The company needs to optimize the architecture to achieve the lowest possible total cost for S3 storage and data transfer without introducing a single point of failure or violating high availability standards. Which solution meets these requirements most cost-effectively?
- AConsolidate the VPC route tables in the `us-east-1` VPC to direct all outbound S3 traffic to a single NAT Gateway located in one public Availability Zone, and continue reading data directly from the `us-west-2` bucket.
- Configure S3 Cross-Region Replication (CRR) from the `us-west-2` bucket to a new S3 bucket in `us-east-1`. Create an S3 Gateway VPC Endpoint in the `us-east-1` VPC. Configure the EKS applications to read from the replicated local bucket in `us-east-1`.Cevap
- CEstablish an AWS Transit Gateway in `us-east-1` and peer it with a Transit Gateway in `us-west-2`. Route the EKS S3 traffic through the Transit Gateway peering connection to access the `us-west-2` bucket using a Gateway VPC Endpoint deployed in `us-west-2`.
- DOrder an AWS Snowball Edge Storage Optimized device to physically transport the initial dataset from `us-west-2` to `us-east-1`, and schedule monthly Snowball shipments to transfer the delta updates.