ecs-health-check-debug

What problem does it solve?

ECS Fargate CDK deployments frequently fail with a ROLLBACK_IN_PROGRESS error when the container health check relies on the curl command, but the Docker image does not include curl installed. This causes health checks to fail repeatedly, containers to restart in a loop, and the ECS service to never stabilize, leading to CDK deployment timeouts and failed releases.

Core Features & Use Cases

• Root Cause Identification: Clearly pinpoints the missing curl dependency in Docker images as the source of ECS health check stabilization failures.
• Multiple Remediation Options: Provides three actionable, platform-agnostic solutions: adding curl to the Dockerfile, modifying the health check command to use tools already present in the image, or using ECS exec for manual container verification.
• Post-Fix Validation: Includes step-by-step AWS CLI commands to confirm curl exists in the running container, check target group health, and review ECS service events to verify the deployment is fully stable.
• Use Case: Perfect for DevOps engineers deploying Node.js or Bun containerized applications to AWS ECS Fargate via CDK who encounter unexpected deployment rollbacks with no clear root cause.

Quick Start

Use this skill to diagnose and fix ECS Fargate CDK deployment failures caused by missing curl in your Docker image for container health checks.