Which combination of steps will resolve the us-east-1 performance issues?
(Choose two.)
Configure the AWS Global Accelerator endpoint for the S3 bucket in eu-west-1. Configure endpoint groups for TCP ports 80 and 443 in us-east-1.
Create a new S3 bucket in us-east-1. Configure S3 cross-Region replication to synchronize from the S3 bucket in eu-west-1.
Use Lambda@Edge to modify requests from North America to use the S3 Transfer Acceleration endpoint in us-east-1.
Use Lambda@Edge to modify requests from North America to use the S3 bucket in us-east-1.
Configure the AWS Global Accelerator endpoint for us-east-1 as an origin on the CloudFront distribution. Use Lambda@Edge to modify requests from North America to use the new origin.
Explanations:
AWS Global Accelerator is used to improve performance for globally distributed users by optimizing routing. However, it cannot be used directly for S3 buckets, as it’s designed for regional endpoints and application traffic.
Creating an S3 bucket in the us-east-1 Region and enabling cross-Region replication will reduce latency by serving data closer to the users in the us-east-1 Region.
Lambda@Edge allows for request modification at CloudFront edge locations, but using it to modify requests to use the S3 Transfer Acceleration endpoint in us-east-1 is unnecessary, as Transfer Acceleration is not optimal for this scenario.
Lambda@Edge can be used to modify requests, redirecting users to the S3 bucket in us-east-1, which would lower latency for users in the us-east-1 Region.
Using AWS Global Accelerator with CloudFront is an incorrect approach because CloudFront already optimizes content delivery globally, and Global Accelerator is not needed for this use case.
From my point of view, the answer is:
Create a new S3 bucket in us-east-1. Configure S3 cross-Region replication to synchronize from the S3 bucket in eu-west-1.
As I understand it, the answer is:
Create a new S3 bucket in us-east-1. Configure S3 cross-Region replication to synchronize from the S3 bucket in eu-west-1.