Private origin
Block all public access stays on. A direct S3 link returns Access Denied.
Project 1 · Live on AWS
Hello from AWS S3 + CloudFront.
Served over HTTPS from a private bucket. The files stay locked in S3. CloudFront is the only door in.
See how it’s built
No public bucket. Redirected to HTTPS.
Edge delivery
CloudFront fetches the files and serves them from locations close to the visitor.
Free HTTPS
A certificate in us-east-1 puts the padlock on your own domain.
The path of a request
Three stops, then the page.
-
01
You open the domain
DNS points the name at the CloudFront distribution, and HTTP is redirected to HTTPS.
-
02
CloudFront asks S3
Origin Access Control signs the request. S3 accepts it only from this distribution.
-
03
index.html loads
The default root object is this page, plus the stylesheet, script, and images beside it.
What you created
A small stack, kept private.
- Amazon S3 Stores the site. Static website hosting stays off.
- Origin Access Control Lets this CloudFront distribution read the bucket.
- Amazon CloudFront Serves the site worldwide and redirects to HTTPS.
- AWS Certificate Manager Issues the certificate in N. Virginia for your domain.
You’re looking at it
This page is the upload.
If the padlock is in the address bar, CloudFront and the certificate are doing their job. If a refresh of a deep link fails later, that is a separate app setting — this site is one file, so the root object is enough.