Which solution will meet these requirements?
Create an Amazon CloudFront distribution in front of the ALB
Deploy an Amazon API Gateway regional API endpoint. Integrate the API endpoint with the ALB
Create an accelerator in AWS Global Accelerator. Add a listener. Configure the endpoint to point to the ALB.
Deploy the ALB and the fleet of EC2 instances to another Region. Use Amazon Route 53 with geolocation routing.
Explanations:
CloudFront is a content delivery network (CDN) that caches content at edge locations, which is beneficial for static content. However, for a latency-sensitive gaming service, CloudFront would not significantly reduce latency for dynamic, real-time game traffic. It is not the best solution for low-latency needs in a global gaming context.
API Gateway is useful for creating API endpoints but is not designed to optimize real-time, low-latency gaming services. Using a regional API Gateway with an ALB would not provide the low-latency performance required, as API Gateway is not tailored for game traffic at scale.
AWS Global Accelerator improves the performance of global applications by routing traffic to the optimal endpoint based on health, geography, and latency. It provides low-latency access for global users by using AWS’s global network and automatically directing traffic to the nearest healthy endpoint, which is ideal for the gaming service’s needs.
Deploying a second ALB and EC2 instances in another region would increase complexity and management overhead. While Route 53 geolocation routing could direct users to the nearest region, this approach introduces cross-region traffic, which can increase latency and affect performance. Global Accelerator is a more efficient solution.
I map out that the answer is:
Create an accelerator in AWS Global Accelerator. Add a listener. Configure the endpoint to point to the ALB.