CloudWatch Metric Guide
Amazon EC2 CloudWatch AlarmsThresholds, failures, and debugging guides
4 CloudWatch metrics covered for Amazon EC2. Each guide includes the recommended alarm threshold, common root causes, and how Nuberio automatically diagnoses it when it fires.
4
metrics covered
AWS/EC2
namespace
5 min
to run a free audit
Amazon EC2 metrics
CPUUtilization
CPUUtilization measures the percentage of allocated EC2 compute units (vCPUs) that are in use on the instance, as reported by the hypervisor.
Threshold
> 80% for 15 consecutive minutes
NetworkIn
NetworkIn measures the number of bytes received by the instance on all network interfaces during the CloudWatch measurement period.
Threshold
Anomaly detection recommended over fixed threshold — alert when NetworkIn exceeds 3 standard deviations above the historical baseline for the same time of day
NetworkOut
NetworkOut measures the number of bytes sent by the instance on all network interfaces during the CloudWatch measurement period.
Threshold
Anomaly detection recommended — alert when NetworkOut exceeds 3 standard deviations above baseline for the same time of day and day of week
StatusCheckFailed
StatusCheckFailed combines the results of both the instance status check (instance software and network configuration) and the system status check (underlying AWS host hardware). A value of 1 means at least one of these checks has failed.
Threshold
> 0 — alarm immediately
Audit your setup
Missing a Amazon EC2 alarm?
The free Nuberio Audit scans your CloudWatch setup and flags missing or misconfigured Amazon EC2 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, DynamoDB, SQS, API Gateway, S3, CloudFront, ElastiCache, and EKS.