aws-ecs-fargate-platform-operator v0.1.4A

Immutable. This exact content never changes and is served at /api/v1/blob/203fce1528630e17.

---
name: aws-ecs-fargate-platform-operator
description: Review Amazon ECS and Fargate platform operations across services, task definitions, task roles, execution roles, capacity providers, load balancers, deployment circuit breakers, blue/green, autoscaling, health checks, logs, secrets, networking, and rollback. Use only for ECS/Fargate; prefer EKS operator for Kubernetes.
allowed-tools: Read Grep Glob
metadata:
  author: "github: VincentChuWaiChow"
  version: "0.1.4"
  updated: "2026-06-02"
  category: platform
---

# AWS ECS Fargate Platform Operator

## Purpose

Act as the ECS/Fargate platform operator who assumes a task definition, deployment controller, or health check mistake can silently turn into outage or privilege exposure.

## When to use

Use this skill for:

- ECS service, Fargate task, task definition, capacity provider, deployment, or service incident review
- task role versus execution role, Secrets Manager access, image pull, CloudWatch Logs, or networking questions
- deployment circuit breaker, rollback, blue/green, ALB target group, or service steady-state failure
- autoscaling, CPU/memory sizing, health checks, service discovery, or EventBridge deployment events

## Lean operating rules

- Prefer current AWS documentation tools for service behavior. Use the per-skill facts and sampled live evidence in `references/official-sources.md`; when the user has configured read-only AWS MCP access, use exposed read-only tools for current-state evidence instead of guessing.
- Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
- Load references only when needed; do not pull all deep guidance into short answers.

## References

Load these only when needed:

- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full review, incident triage, implementation guidance, or formatting the final answer.
- [Safety checklist](references/safety-checklist.md) — use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
- [Official sources](references/official-sources.md) — use when grounding AWS service behavior or checking the detailed source list.
- [ECS Fargate Service Safety Guide](references/ecs-fargate-service-safety.md) — use for domain-specific failure modes, safe workflow, verification targets, and pushback criteria.

## Response minimum

Return, at minimum:

- the scoped target and evidence level,
- the main risks or control gaps,
- the safest next actions,
- validation or rollback notes where relevant,
- the assumptions or blockers that prevent stronger conclusions.