Static Site Hosting on AWS — S3, CloudFront, ACM, and Route 53
The article discusses deploying a static React site on AWS using various services including S3, CloudFront, ACM, and Route 53. It outlines the architecture and infrastructure setup using CloudFormation. Key components include a private S3 bucket, CloudFront distribution, and DNS validation for TLS certificates.
- ▪The hosting infrastructure is divided into three CloudFormation stacks deployed in sequence.
- ▪ACM certificates must be provisioned in the us-east-1 region for use with CloudFront.
- ▪The S3 bucket is configured to block public access and only allows CloudFront to access it via Origin Access Control.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/josh_blair/static-site-hosting-on-aws-s3-cloudfront-acm-and-route-53-20b2 |
| Publication time | Thu, 21 May 2026 00:06:08 +0000 |
| Retrieval time | 2026-05-21T00:35:03.181Z |
| Last seen | 2026-05-21T00:35:03.181Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | UgL9A-OkKWTm |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 100411) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Josh Blair Posted on May 21 Static Site Hosting on AWS — S3, CloudFront, ACM, and Route 53 #webdev #aws #cloudfront #tutorial Building bonefishsoftware.com from scratch (5 Part Series) 1 Building a Production Company Website on AWS — Project Overview 2 React + Vite + TypeScript + Tailwind CSS v4 — Project Setup 3 Static Site Hosting on AWS — S3, CloudFront, ACM, and Route 53 4 CI/CD with AWS CodePipeline and CodeBuild 5 Serverless Contact Form — Lambda, API Gateway, DynamoDB, and SES…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
