ecs-reconlisted

ECS environment reconnaissance and discovery. Detects compute and capacity providers, task definitions, deployment configuration, auto scaling, networking, security posture, observability, and IaC/CI-CD tooling. Use when someone asks about their ECS environment, wants to describe a cluster, inspect a service, or document task definitions — even without naming the skill. Applies to Amazon ECS, not Amazon EKS (use eks-recon). Discovers current state only — does not score, audit, or design. Skip for operational audits and GREEN/AMBER/RED scoring (ecs-operation-review), deployment-model design, launch-type selection, and ECS best practices (ecs-architect), deployment strategy design and CI/CD engineering (ecs-devops), GPU/ML workloads (ecs-genai), security and compliance (ecs-security), cost/TCO (ecs-cost-intelligence, once available), observability design (ecs-observability), and replatform/migration (ecs-modernize, once available).
aws-samples/sample-apex-skills · ★ 37 · DevOps & Infrastructure · score 73

Install: claude install-skill aws-samples/sample-apex-skills

# ECS Reconnaissance Discover everything about an ECS environment. Run this skill to gather comprehensive context about clusters, services, and their tasks before making any decisions, changes, or recommendations. Standalone (`run-task`) and scheduled (EventBridge) tasks are not discovered — discovery enumerates workloads via `list-services`. ## When to Use This Skill **Run this skill when the user:** - Asks about their ECS environment ("what clusters do I have?", "describe my ECS setup") - Wants to understand their service configuration ("what launch type?", "how is it deployed?") - Plans to modify a service and needs current-state context first - Asks to document or review their ECS resources - Needs task definition details, scaling policies, or networking config - Mentions an ECS cluster or service and seems to need context **Also trigger this skill when:** - Another workflow needs ECS environment information as input - User mentions ECS and needs discovery before recommendations - You need to understand the ECS setup before giving guidance **Do NOT use this skill for:** - **Cost scoring or efficiency analysis** — belongs to `ecs-cost-intelligence` (once available) - **Security auditing or compliance scoring** — belongs to `ecs-security` - **Best-practices evaluation or maturity ratings** — belongs to `ecs-operation-review` - **Migration planning (replatform/refactor onto ECS)** — belongs to `ecs-modernize` (once available) - **Amazon EKS requests** — belongs to `eks-