CHAPTER 02 / FROM NAME TO OBJECT

Follow the
request.

Trace a request from the domain name through Route 53 and ACM-backed HTTPS to CloudFront and its authorized S3 origin. Follow each handoff and identify the configuration that makes it work.

Namecheap delegates DNS to Route 53, which aliases the domain to CloudFront. ACM supplies CloudFront’s TLS certificate. CloudFront uses signed OAC requests to read private S3 objects.
01

Find the destination

The visitor requests your custom domain. DNS resolves the Route 53 alias to CloudFront. The domain registrar’s nameservers must delegate to the correct public hosted zone.

02

Open a trusted connection

The browser verifies that the TLS certificate is trusted and matches the hostname. HTTP requests are redirected to HTTPS by the distribution’s viewer protocol policy.

03

Read through the authorized origin

On an origin fetch, CloudFront signs its request. S3 evaluates the bucket policy, which permits GetObject for the CloudFront service principal only when the source distribution ARN matches.

04

Return a page, then verify it

CloudFront returns the object. The verification tools check status codes, content hashes, headers, certificate trust, DNS records, and anonymous S3 denial. A claim from an agent is not a substitute for these observations.