CloudWatch Metric Guide
Amazon ECS CloudWatch AlarmsThresholds, failures, and debugging guides
3 CloudWatch metrics covered for Amazon ECS. Each guide includes the recommended alarm threshold, common root causes, and how ConvOps automatically diagnoses it when it fires.
3
metrics covered
AWS/ECS
namespace
9
verification checks
Amazon ECS metrics
CPUUtilization
CPUUtilization for ECS measures the percentage of CPU units reserved by the tasks in a service that are in use, averaged across the tasks in the service.
Threshold
> 85% sustained for 3 minutes
MemoryUtilization
MemoryUtilization for ECS measures the percentage of memory reserved by the tasks in a service that is in use, averaged across the running tasks.
Threshold
> 85% averaged across the service
RunningTaskCount
RunningTaskCount reports the number of tasks in the RUNNING state for an ECS service. Tasks not in RUNNING are either pending, provisioning, deprovisioning, or stopped.
Threshold
< desired task count for the service
Audit your setup
Missing a Amazon ECS alarm?
The free ConvOps Audit scans your CloudWatch setup and flags missing or misconfigured Amazon ECS alarms in 5 minutes. No credit card. Read-only access.
Looking for alarms across other AWS services? View the full CloudWatch metric guide — thresholds and debugging guides for RDS, Lambda, ECS, ALB, EC2, and DynamoDB.
When a Amazon ECS alarm fires, ConvOps Diagnose reads CloudWatch Logs, CloudTrail, and resource state to deliver a plain-English root cause to WhatsApp or Slack in under 60 seconds. See how ConvOps Diagnose works →