Which solution meets these requirements?
Add an Amazon CloudFront distribution. Configure the ALB as the origin.
Add an Amazon API Gateway edge-optimized API endpoint to expose the APIs. Configure the ALB as the target.
Add an accelerator in AWS Global Accelerator. Configure the ALB as the origin.
Deploy the APIs to two additional AWS Regions: eu-west-1 and ap-southeast-2. Add latency-based routing records in Amazon Route 53.
Explanations:
While adding a CloudFront distribution can improve latency by caching responses closer to users, it may not handle non-standard REST methods effectively, which could lead to issues with API functionality.
API Gateway can manage RESTful APIs well but might not be suitable for non-standard methods like LINK, UNLINK, LOCK, and UNLOCK. Additionally, it adds complexity and operational overhead.
AWS Global Accelerator can help optimize the path to the ALB from users worldwide by routing traffic to the nearest AWS edge location, improving response times with minimal operational overhead.
Deploying APIs to additional regions increases complexity and operational overhead. Although it can help with latency, it requires significant management and might not be necessary if Global Accelerator can resolve the issue.
From my perspective, the answer is:
Add an accelerator in AWS Global Accelerator. Configure the ALB as the origin.
It appears that the answer is:
Add an accelerator in AWS Global Accelerator. Configure the ALB as the origin.