What should the company do to meet this requirement?
Use the EC2 instances in multiple edge locations.
Use an Application Load Balancer with the EC2 instances configured as the target.
Use the EC2 instances in the same Availability Zone but in different AWS Regions.
Use Amazon Cloud Front with the EC2 instances configured as the source.
Explanations:
Using EC2 instances in multiple edge locations is not directly feasible, as EC2 instances must be in a VPC within a specific region. Edge locations are used by AWS services like CloudFront, not for hosting EC2 instances.
An Application Load Balancer can distribute traffic to EC2 instances, but it does not inherently provide low latency to global users, as it operates within a specific region and may not cache content or optimize delivery for users far from the region.
Using EC2 instances in the same Availability Zone but in different AWS Regions is not practical; instances in one AZ cannot serve users in another region. Additionally, latency would not improve by just spreading instances across regions without leveraging a global delivery service.
Amazon CloudFront is a Content Delivery Network (CDN) that caches content at edge locations worldwide, significantly reducing latency for users globally. Configuring EC2 instances as the origin for CloudFront allows for efficient delivery of a static website to a global audience.
I chart that the answer is:
Use Amazon Cloud Front with the EC2 instances configured as the source.