A company serves a dynamic website from Amazon EC2 instances behind an Application Load Balancer in the us-west-1 Region. The site must support multiple languages and is experiencing high latency for users in other parts of the world. The company wants faster global performance without recreating the architecture across multiple Regions. What should a solutions architect do?

Configuring an Amazon CloudFront distribution with the ALB as the origin is the most effective solution. CloudFront is a global content delivery network (CDN) that caches content at edge locations worldwide, significantly reducing latency for global users. By setting the cache behavior to cache based on the Accept-Language header, CloudFront can serve language-specific content directly from the edge, improving performance without requiring architectural changes in multiple regions. Replacing the architecture with S3 is not suitable for a dynamic website. API Gateway is designed for APIs, not typically for serving entire dynamic websites, and its caching mechanism might not be as optimized for full-page content delivery as CloudFront. Launching EC2 instances in each region with NGINX adds operational complexity and cost, essentially recreating the problem CloudFront solves more efficiently.