Answer: Use Amazon CloudFront with the EC2 instances configured as the source.

## Explanation Amazon CloudFront is AWS's Content Delivery Network (CDN) service designed specifically to minimize latency for users accessing content globally. Here's why option C is correct: ### Key Points: 1. **CloudFront's Global Edge Network**: CloudFront has a global network of edge locations that cache content closer to end users, reducing latency significantly. 2. **Static Website Optimization**: For static websites, CloudFront can cache content at edge locations, serving it directly to users without hitting the origin EC2 instances for every request. 3. **Origin Configuration**: EC2 instances can be configured as the origin for CloudFront, allowing CloudFront to fetch content from EC2 when needed and cache it at edge locations. ### Why Other Options Are Incorrect: - **Option A**: EC2 instances are not available in edge locations. Edge locations are specifically for services like CloudFront, not for running EC2 instances. - **Option B**: Placing EC2 instances in the same Availability Zone but different Regions doesn't address global latency. Users far from those Regions would still experience high latency. - **Option D**: Using different AWS accounts doesn't reduce latency. The physical location of the instances is what matters for latency, not the account structure. ### Best Practice: For global static websites, the recommended AWS architecture is: 1. Host static content on EC2 instances (or better yet, Amazon S3 for cost efficiency) 2. Configure CloudFront as a CDN with the EC2/S3 as the origin 3. Enable caching at CloudFront edge locations 4. Use Route 53 for DNS routing if needed This architecture ensures users get content from the nearest edge location, minimizing latency regardless of their geographic location.

Author: Ritesh Yadav