← ClaudeAtlas

aws-serverlesslisted

Deploy any web project to AWS serverless infrastructure (S3 + CloudFront for static sites, Lambda + API Gateway for containers) at ~$1-3/month with automatic HTTPS and CI/CD
NotDannyCrawford/aws-serverless · ★ 0 · DevOps & Infrastructure · score 53
Install: claude install-skill NotDannyCrawford/aws-serverless
# AWS Serverless Deploy Skill ## Philosophy **Pay only for what you use.** No idle servers, no fixed monthly costs. This skill deploys web projects to AWS serverless infrastructure where costs scale to zero when there's no traffic. Two paths, one workflow: - **Static sites** (React, Vue, Next.js static export, plain HTML) → S3 + CloudFront (~$0.50/month) - **Container apps** (Express, Flask, FastAPI, Django, Go APIs) → Lambda + API Gateway + CloudFront (~$1-3/month) ### Skip-If-Done Principle At the start of every phase, check if the user has already completed it. Don't force unnecessary setup. If S3 bucket exists, skip creation. If Lambda is already deployed, skip to update. ### When NOT to Use This Skill - Apps that need persistent WebSocket connections (use EC2 instead) - Apps that need more than 10GB RAM or 15-minute execution time (Lambda limits) - Apps with heavy background processing (use EC2 or ECS) - For those cases, use the `aws-deploy` skill instead (EC2-based, ~$12-15/month) --- ## Phase 1: Pre-flight Check > Reference: `references/preflight.md` **Goal:** Ensure the project is clean, version-controlled, and safe to deploy. **Ask first:** "Is your code already pushed to a GitHub repository?" ### Steps 1. **Git initialized?** - Check for `.git/` directory - If missing: `git init`, create initial commit 2. **GitHub remote?** - Check `git remote -v` for origin - If missing: guide user to create repo and add remote - Verify code is pushed: `