What should a solutions architect recommend to accomplish this?
Place the EC2 instances behind Network Load Balancers (NLBs) in each Region. Create an accelerator using AWS Global Accelerator. Use the NLBs as endpoints for the accelerator.
Place the EC2 instances behind Application Load Balancers (ALBs) in each Region. Create an accelerator using AWS Global Accelerator. Use the ALBs as endpoints for the accelerator.
Place the EC2 instances behind Network Load Balancers (NLBs) in each Region. Create an Amazon CloudFront distribution with an origin that uses Amazon Route 53 latency-based routing to route requests to the NLBs.
Place the EC2 instances behind Application Load Balancers (ALBs) in each Region. Create an Amazon CloudFront distribution with an origin that uses Amazon Route 53 latency-based routing to route requests to the ALBs.
Explanations:
Network Load Balancers (NLBs) support UDP traffic and can efficiently route it to EC2 instances. AWS Global Accelerator enhances availability and performance by providing a static IP address and directing traffic to the NLBs based on health checks, improving latency and failover across multiple regions.
Application Load Balancers (ALBs) do not support UDP traffic as they are designed for HTTP/HTTPS protocols. Therefore, using ALBs would not be suitable for a stateless UDP-based workload.
While NLBs are suitable for UDP traffic, CloudFront is primarily used for HTTP/HTTPS and cannot directly handle UDP workloads. Additionally, CloudFront requires a specific origin setup, which does not align with the requirement for a stateless UDP workload.
Similar to option B, Application Load Balancers (ALBs) do not support UDP traffic, making them unsuitable for this scenario. Moreover, CloudFront is not designed to handle UDP-based workloads, which invalidates the overall solution.