aws-infrastructure

# aws-infrastructure ## When to use Use this skill when working with AWS infrastructure, deployment configurations, ECS task definitions, or environment-specific settings. Do NOT use when: - Local development setup (use `docker` skill) - Application code changes ## Procedure: Modify AWS infrastructure 1. Read the `.aws/` directory (or equivalent) for env configs and templates. 2. Read CI/CD workflows (e.g., `.github/workflows/`) for the deployment pipeline. 3. Check the env-specific vars files. 4. **Read project-level overrides** — check `agents/overrides/skills/aws-infrastructure.md` for project-specific service names, prefixes, and infrastructure details. ## Architecture overview ### Environments (typical setup) | Environment | Trigger | Notes | |---|---|---| | Review | PR with label | Ephemeral, per-branch | | Stage | Push to `main` | Persistent, pre-production | | Production | Release tag | Persistent, live | ### Common AWS services | Service | Purpose | |---|---| | **ECS Fargate** | Container orchestration (no EC2 instances) | | **ECR** | Docker image registry | | **EFS** | Shared filesystem (private + public access points) | | **Secrets Manager** | `.env` file storage per env | | **IAM Roles** | OIDC-based GitHub Actions authentication | | **VPC** | Networking (security groups, subnets) | ### Vars file structure Environment-specific config files (e.g., `.aws/*.vars.yaml`) typically contain: ```yaml AWS: GlobalPrefix: {project}-{env} # Resource naming ...