What should a solutions architect do to accomplish this?
Copy the website content to an Amazon S3 bucket. Configure the bucket to serve static webpage content. Replicate the S3 bucket to multiple AWS Regions.
Copy the website content to an Amazon S3 bucket. Configure the bucket to serve static webpage content. Configure Amazon CloudFront with the S3 bucket as the origin.
Copy the website content to an Amazon EBS-backed Amazon EC2 instance running Apache HTTP Server. Configure Amazon Route 53 geolocation routing policies to select the closest origin.
Copy the website content to multiple Amazon EBS-backed Amazon EC2 instances running Apache HTTP Server in multiple AWS Regions. Configure Amazon CloudFront geolocation routing policies to select the closest origin.
Explanations:
While copying the content to S3 and configuring it for static web hosting is correct, replicating the S3 bucket across multiple regions is unnecessary for a static website, as S3 already provides high availability and durability. This option does not include a CDN for faster global access.
This option utilizes Amazon S3 for hosting the static website, which is cost-effective, and integrates Amazon CloudFront, a Content Delivery Network (CDN), to cache content at edge locations worldwide, ensuring faster load times for users globally.
Using an EBS-backed EC2 instance is more complex and expensive compared to S3 for static content. While geolocation routing can help users access the closest instance, this approach does not leverage the benefits of a CDN for speed and efficiency.
This option is also more complex and costly due to the use of multiple EC2 instances across regions. While it incorporates geolocation routing, it lacks the efficiency and cost-effectiveness of using S3 and CloudFront for a static website.
I design that the answer is:
Copy the website content to an Amazon S3 bucket. Configure the bucket to serve static webpage content. Configure Amazon CloudFront with the S3 bucket as the origin.