Which solution will meet these requirements?
Create Application Load Balancers (ALBs) in each Region to replace the existing NLBs. Register the existing EC2 instances as targets for the ALBs in each Region.
Configure Amazon Route 53 to route equally weighted traffic to the NLBs in each Region.
Create additional NLBs and EC2 instances in other Regions where the company has large customer bases.
Create a standard accelerator in AWS Global Accelerator. Configure the existing NLBs as target endpoints.
Explanations:
ALBs operate at Layer 7 and are more suitable for HTTP/HTTPS traffic, whereas the existing setup uses NLBs for Layer 4 (TCP/UDP). Switching to ALBs would not improve latency or provide any global acceleration.
Route 53 with equally weighted traffic routing would distribute traffic but lacks any latency-based routing or acceleration capabilities, which would not reduce end-to-end load time.
Adding more NLBs and EC2 instances in other Regions could improve local availability but would not directly optimize global latency for a geographically dispersed customer base.
AWS Global Accelerator provides a global network path to route traffic, which reduces end-to-end latency by using the AWS global network backbone. Configuring NLBs as target endpoints improves load time for global users.