What should a solutions architect do to meet these requirements?
Deploy Amazon CloudFront to support the global traffic. Configure CloudFront with an origin group to allow access to EC2 instances in multiple Regions.
Deploy an Application Load Balancer in one Region to distribute traffic to EC2 instances in each Region that hosts the game’s backend instances.
Deploy Amazon CloudFront to support an origin access identity (OAI). Associate the OAI with EC2 instances in each Region to support global traffic.
Deploy a Network Load Balancer in each Region to distribute the traffic. Use AWS Global Accelerator to route traffic to the correct Regional endpoint.
Explanations:
Amazon CloudFront is primarily used for caching and delivering content with low latency, but it is not designed to handle UDP traffic directly. While it can improve access speed for HTTP/S traffic, it does not facilitate the necessary low-latency communication for UDP-based games.
An Application Load Balancer (ALB) is designed for HTTP/HTTPS traffic and does not support UDP. Therefore, it would not be suitable for handling the UDP traffic required by the multiplayer game, making it an incorrect choice for achieving low latency and high availability for this scenario.
Similar to Option A, Amazon CloudFront is not designed for UDP traffic, and configuring it with an origin access identity (OAI) does not address the requirement for low-latency, real-time communication in a multiplayer game. CloudFront works better with HTTP/S protocols rather than UDP.
Deploying a Network Load Balancer (NLB) in each Region is suitable for handling UDP traffic as NLB supports both TCP and UDP protocols. Using AWS Global Accelerator further enhances performance by routing user traffic to the nearest regional endpoint based on health and routing policies, ensuring low latency and high availability across multiple regions.
From my perspective, the answer is:
Deploy a Network Load Balancer in each Region to distribute the traffic. Use AWS Global Accelerator to route traffic to the correct Regional endpoint.