Which solution will improve global performance with the LEAST operational overhead?
Set up an Amazon CloudFront distribution that uses the ALB as the origin server. Configure Route 53 to create a DNS alias record that points the application’s domain name to the CloudFront distribution URL.
Launch more EC2 instances behind the ALConfigure the ALB to use session affinity (sticky sessions). Create a Route 53 alias record for the ALB by using a geolocation routing policy.
Create an AWS Client VPN endpoint in the VPInstruct users to connect to the VPN to access the application. Create a Route 53 alias record for the VPN endpoint. Configure Route 53 to use a geolocation routing policy.
Deploy the application to multiple Regions across the world. Create a Route 53 alias record for the ALB by using a latency-based routing policy.
Explanations:
Using Amazon CloudFront as a CDN improves global performance by caching content at edge locations close to users. This reduces latency and offloads traffic from the origin server (ALB). Configuring Route 53 to point to CloudFront further enhances performance without adding significant operational overhead.
Launching more EC2 instances and using session affinity (sticky sessions) increases the backend capacity but does not address global performance effectively. Geolocation routing in Route 53 can direct traffic based on the user’s location, but it does not optimize the content delivery speed globally, as users may still experience latency.
Creating an AWS Client VPN endpoint requires users to connect to the VPN, which adds complexity and overhead to the user experience. While this method may secure access, it does not inherently improve global performance for all users compared to using a CDN. Additionally, using a geolocation routing policy for a VPN endpoint is not efficient for improving application performance.
Deploying the application in multiple AWS Regions does enhance performance by reducing latency through proximity to users. However, it increases operational overhead due to the need for managing multiple deployments. Latency-based routing is beneficial, but this option involves more complexity and management compared to using a single CloudFront distribution.
I think the answer is:
Set up an Amazon CloudFront distribution that uses the ALB as the origin server. Configure Route 53 to create a DNS alias record that points the application’s domain name to the CloudFront distribution URL.