THE ARCHITECTURE

Follow every
request.

See how a domain, a certificate, delivery, and storage fit together.

CONTENT DELIVERY PATH
A visitor uses the domain resolved by Route 53, connects over HTTPS to CloudFront using an ACM certificate, and receives content from private S3 storage

A conceptual architecture—not a live deployment status display.

ONE REQUEST, DISTINCT RESPONSIBILITIES

Every connection has a purpose.

  1. 01

    Find the website

    A visitor enters the registered domain. Route 53 DNS records point toward the configured CloudFront distribution. Namecheap handles domain registration.

  2. 02

    Establish a secure connection

    CloudFront presents the domain’s ACM certificate. HTTPS must work correctly, and requests over HTTP must redirect to HTTPS.

  3. 03

    Deliver the content

    CloudFront serves the website files stored in S3. All five content pages, shared navigation, styles, scripts, and images should load correctly.

  4. 04

    Keep the origin protected

    The S3 bucket does not allow anonymous public access. Direct anonymous access to protected website objects must be denied and recorded during verification.

YOUR TURN

Can you match each service to its job?

Try the practice lab