← ClaudeAtlas

ecs-buildlisted

Use when building Amazon ECS infrastructure with Terraform, generating apply-ready code for ECS clusters, services, and task definitions across three capacity models — Fargate (FARGATE_SPOT as capacity provider), EC2 Auto Scaling group providers, and ECS Managed Instances. Covers rolling/blue-green/linear/canary deployment config, Express services, Service Connect, private/VPC-endpoint-only networking, secrets, and Graviton. Also use when (1) wiring a Managed Instances capacity provider and its infrastructure IAM role, (2) mixing FARGATE and FARGATE_SPOT in a strategy, (3) rendering the Terraform deployment configuration for a blue/green, linear, or canary strategy, (4) generating VPC endpoints for private or air-gapped ECS, (5) configuring Application Auto Scaling, or (6) rendering the migration of a service from launch type to capacity providers. Skip for EKS/Kubernetes builds (use eks-build), design and launch-type selection (use ecs-architect), CI/CD pipelines and release strategy (use ecs-devops).
aws-samples/sample-apex-skills · ★ 37 · DevOps & Infrastructure · score 73
Install: claude install-skill aws-samples/sample-apex-skills
# ECS Build Generate complete, production-ready Amazon ECS infrastructure projects in Terraform. All generated code is `terraform apply`-ready with zero manual fixups. All generated Terraform code MUST follow the conventions from these companion skills: - **terraform-skill** -- resource block ordering, variable conventions, file organization, version constraints Scope: **Terraform only.** For CDK-based ECS generation, this skill does not apply -- point the user at the AWS CDK `ecs-patterns` constructs and the `aws-containers` skill in [aws/agent-toolkit-for-aws](https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-containers). ECS Anywhere (`EXTERNAL` launch type) is not generated by this skill -- it has no capacity providers, no service load balancing, and no awsvpc mode; advise rolling-update-only guidance and route deployment questions to `ecs-devops`. ## When to Use - Generating ECS Terraform code from requirements (new project) - Scaffolding an ECS cluster with Fargate, EC2 (ASG), or Managed Instances capacity providers - Wiring the ECS infrastructure IAM role for Managed Instances, EBS task volumes, or Service Connect TLS - Generating services with native ROLLING / BLUE_GREEN / LINEAR / CANARY deployment configuration - Building task definitions with correct execution-role/task-role separation and secrets injection - Generating private/air-gapped ECS networking (VPC endpoints, no NAT) - Adding Application Auto Scaling (target tracking, ste