A company serves a static marketing website made of HTML, images and JavaScript from an Amazon S3 bucket in eu-west-1. Visitors are spread across Europe, North America and Asia, and pages in distant Regions load slowly. The team wants to cache this cacheable content at edge locations close to viewers and serve it over HTTPS with the least operational overhead. Which service should they place in front of the bucket?
- AAWS Global Accelerator with the S3 bucket added as an endpoint, so viewers connect to static anycast IP addresses routed to the nearest edge location.
- BAmazon CloudFront with the S3 bucket as the origin, so cacheable objects are stored at edge locations and served to viewers over HTTPS from the nearest point of presence. Correct
- CAn Application Load Balancer in each Region pointing at the S3 bucket, so viewers reach a regional balancer that forwards their request on to the static content.
- DAmazon Route 53 latency-based records that resolve viewers to the S3 website endpoint giving them the lowest measured network latency to the bucket Region.
Why A is wrong: Global Accelerator improves the network path for TCP and UDP traffic but does not cache content at the edge, so repeated requests still travel to the origin Region and the slow loads for static assets remain.
Why B is correct: CloudFront is the content delivery network that caches static objects at edge locations near viewers and serves them over HTTPS, which directly reduces latency for the cacheable website content with little ongoing management.
Why C is wrong: An Application Load Balancer distributes requests across compute targets within one Region and cannot use an S3 bucket as a target, so it neither caches objects nor places content closer to distant viewers.
Why D is wrong: Latency routing only steers DNS toward the bucket's single Region and caches nothing, so viewers far from eu-west-1 still fetch every object across a long path with no edge acceleration.