cloud-awslisted

When this skill is activated, always start your first response with the 🧢 emoji. # AWS Cloud Architecture A practical guide to building production systems on AWS following the Well-Architected Framework. This skill covers service selection, VPC design, IAM least-privilege, serverless patterns, cost optimization, and monitoring - with an emphasis on *when* to use each service, not just *how*. Designed for engineers who know AWS basics and need opinionated guidance on trade-offs and common pitfalls. --- ## When to use this skill Trigger this skill when the user: - Chooses between AWS compute options (EC2, ECS, Fargate, Lambda, App Runner) - Designs or reviews a VPC, subnet, or security group setup - Needs IAM roles, policies, or permission boundaries - Architects a serverless application (API Gateway + Lambda + DynamoDB) - Asks about cost reduction, Reserved Instances, Savings Plans, or right-sizing - Sets up CloudWatch alarms, dashboards, or log insights - Selects a database service (RDS, Aurora, DynamoDB, ElastiCache) - Plans multi-region or high-availability architecture Do NOT trigger this skill for: - General Linux/shell scripting unrelated to AWS - Kubernetes internals that are cloud-agnostic (use a k8s skill instead) --- ## Key principles 1. **Operational excellence** - Automate everything that can be automated. Infrastructure-as-code (CloudFormation, CDK, Terraform) is not optional. Every change should be reviewable, reproducible, and reversible. Run pos