⚡

Serverless Full-Stack

CloudFront + S3 static frontend, plus a separate HTTP API (API Gateway → Lambda → DynamoDB) with Cognito auth.

What you can build with this

A SPA (React/Vue/etc.) served from CloudFront + S3, backed by a serverless HTTP API and Cognito user accounts. The API is deliberately NOT routed through CloudFront: this engine only supports a REST API (v1) as a CloudFront origin, and this template uses the cheaper/modern HTTP API (v2) — so the API gets its own execute-api domain instead of a fictional /api/* path behind the CDN. Cognito ships with the OAuth Hosted UI OFF (no callback URL to give it yet, before you have a domain) — your frontend authenticates directly against the User Pool via the SDK (USER_SRP_AUTH), which needs no redirect URL at all.

Deployment timing

After you run the deploy command, resources come online at different times. Check the validation steps in order.

Resource	Ready in
DynamoDB Table, User Pool, S3 Bucket	Immediate
Lambda Function + IAM Role	30–60 sec
HTTP API + Routes + Stage	1–2 min
CloudFront Distribution created	2–3 min (stack CREATE_COMPLETE)
CloudFront fully propagated globally	5–15 min after CREATE_COMPLETE

DNS / Certificate note: ACM certificates for CloudFront must be requested in us-east-1. The API's own execute-api domain is separate from your CloudFront domain by design — point a subdomain like api.yourapp.com at it via Route53 + a Custom Domain Name on the HTTP API if you want a matching domain, or call the execute-api URL directly.

CloudFormation parameters

These are the values you will fill in when deploying the exported template. Changing these does not break the template — that is the point.

Parameter	What to provide	Example
Environment	Environment tag applied to resources (does not rename them)	dev