aws-ecs-monitor

Monitors AWS ECS service health and analyzes CloudWatch logs for error diagnosis.

1|Updated May 10, 2026
One-click install
npx skills add https://github.com/Tgoldi/claude-skills --skill aws-ecs-monitor-tgoldi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-ecs-monitor
Source: https://github.com/Tgoldi/claude-skills/tree/main/aws-ecs-monitor
Command: npx skills add https://github.com/Tgoldi/claude-skills --skill aws-ecs-monitor-tgoldi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually checking ECS service status, ALB target health, SSL certificates, and digging through CloudWatch logs to find the root cause of production issues is slow and error-prone. This Skill automates production health monitoring and log analysis for AWS ECS clusters. ## Core Features & Use Cases - Health Checks: Probes your domain over HTTP, compares ECS desired vs running task counts, checks ALB target group health, and tracks SSL certificate expiry. - Log Analysis: Pulls CloudWatch logs and categorizes errors (panics, fatals, OOM, timeouts, 5xx), detects container restarts, and filters health-check noise. - Auto-Diagnosis: When the health check detects failures, it automatically runs deep log analysis on the affected services. - Use Case: Your production API starts returning 500s. Run the health monitor, which flags the degraded service and automatically analyzes its CloudWatch logs to surface the panic or OOM errors causing the outage. ## Quick Start Set the ECS_CLUSTER environment variable to your cluster name and ask the assistant to run an ECS health check and diagnose any failing services from CloudWatch logs.

Frequently Asked Questions about aws-ecs-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor AWS ECS service health from the command line?

Set the ECS_CLUSTER environment variable and run scripts/ecs-health.sh. It checks ECS desired vs running task counts, ALB target group health, domain HTTP status, and SSL certificate expiry, writing results to a JSON state file.

How to analyze CloudWatch logs for ECS container errors?

Run scripts/cloudwatch-logs.sh with the diagnose command to pull logs and categorize errors such as panics, fatals, OOM, timeouts, and HTTP 5xx responses. Use the errors or restarts commands for narrower checks, and --minutes to control the time window.

What IAM permissions are required for ECS health monitoring?

The scripts require ecs:ListServices, ecs:DescribeServices, elasticloadbalancing:DescribeTargetGroups, elasticloadbalancing:DescribeTargetHealth, logs:FilterLogEvents, and logs:DescribeLogGroups. The aws CLI must be configured with credentials holding these permissions.

Can I monitor ECS services in a custom log group pattern?

Yes. Set the ECS_LOG_PATTERN environment variable, for example /ecs/prod/{service}, and the scripts resolve each service's log group by substituting the service name. The default pattern is /ecs/{service}.

Why does the health check report degraded when tasks are running?

A degraded status occurs when running task count is below desired count or when ALB target groups have unhealthy targets. Check the issues array in the generated ecs-health.json state file for the specific failing check.