استضافة المواقع الثابتة وتسليمها عبر CDN

Beyond storing files, S3 can host a static website, HTML, CSS, JS, and images, with no servers to manage. It is cheap, scalable, and a perfect fit for single-page apps and documentation sites.

You enable the static website hosting feature on the bucket and specify an index document (the home page) and an error document.

The index document (often index.html) is served for the root and folder URLs. The error document handles 4xx responses, useful for SPA routing where you point errors back to index.html.

Sync your build output into the bucket. The AWS CLI sync command uploads only changed files.

S3 serves files with the Content-Type stored as metadata. If a CSS file is served as plain text, browsers ignore it. The CLI usually infers types, but verify for unusual extensions.

Static hosting exposes a regional website endpoint URL. It is HTTP only and not ideal for production, which is exactly why we add a CDN next.

CloudFront is AWS's content delivery network. It caches your site at edge locations worldwide, so users get fast responses from a nearby server and your bucket sees less load.

A CloudFront distribution points at an origin (your S3 bucket). CloudFront fetches from the origin on a cache miss and serves the cached copy on subsequent requests.

CloudFront gives you free HTTPS via AWS Certificate Manager and lets you attach a custom domain like www.example.com, things the raw S3 endpoint cannot do.

For security, keep the bucket private and let only CloudFront read it using an Origin Access Control (OAC). Visitors reach content through the CDN, never the bucket directly.

CloudFront caches aggressively. After deploying new content, invalidate the cache so users get the latest version instead of a stale copy.

Test your static hosting knowledge.

You can now ship a static site on AWS:

• Enable S3 static website hosting with index/error documents.
• aws s3 sync deploys your build.
• CloudFront adds edge caching, HTTPS, and custom domains.
• Use OAC to keep the bucket private and invalidate the cache on deploy.