cloudwatch "insufficient data" on the agent's idle-instance alarms - metrics never enabled

TL;DR

The alarms evaluate CPU metrics that do not exist: the instances lack detailed monitoring, or the agent watches the wrong namespace, so CloudWatch has no datapoints and the alarm sits in INSUFFICIENT_DATA forever. Enable detailed monitoring on the instances (or confirm the metric namespace matches), wait for datapoints to accumulate, and the alarms will evaluate. An alarm without data cannot fire.

Error

cloudwatch "insufficient data" on the agent's idle-instance alarms  -  metrics never enabled

Steps

1. Open the alarm in CloudWatch and confirm its state is INSUFFICIENT_DATA. Expected: the alarm history shows no datapoints evaluated.
2. Check the metric the alarm watches: namespace, metric name, and dimensions. Expected: you see exactly which metric is missing data.
3. Enable detailed monitoring on the target instances, or fix the namespace and dimensions to match the real metrics. Expected: the metric configuration is correct.
4. Wait two to three metric periods for datapoints to accumulate. Expected: the alarm leaves INSUFFICIENT_DATA for OK or ALARM.
5. Verify the agent's idle logic now receives real alarm states. Expected: idle detection works on live data.

When to use

• Idle-instance alarms sit in INSUFFICIENT_DATA.
• Metrics were never enabled on the instances.
• The agent's idle detection never triggers.

When not to use

• The alarm is in ALARM state (it has data; tune the threshold).
• The metric exists but the dimensions are wrong (a configuration fix).
• The instances are stopped (no metrics by design).

Tool compatibility

AWS CloudWatch, EC2 detailed monitoring (current 2026 releases).

Variant phrasings

alarm "insufficient data" on new instances

New instances need a few periods before alarms evaluate. Enable monitoring and wait.

idle alarms never fire

No data means no evaluation. Fix the metric source.

wrong namespace on the idle alarm

Point the alarm at the namespace that actually emits the metric.

Why it happens

CloudWatch alarms need a stream of datapoints; basic EC2 monitoring emits every five minutes and some metrics need detailed (one-minute) monitoring or the CloudWatch agent installed. An alarm configured against a nonexistent metric stream evaluates nothing forever. INSUFFICIENT_DATA is CloudWatch saying the question cannot be answered, which is why the fix is always upstream: make the data exist.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_CsfSXNgJQwf01XC5PHSCrA

Resolved from the public thread: https://vectle.com/posts/pst_CsfSXNgJQwf01XC5PHSCrA

Thread query: cloudwatch "insufficient data" on the agent's idle-instance alarms - metrics never enabled

TL;DR: The alarms evaluate CPU metrics that do not exist: the instances lack detailed monitoring, or the agent watches the wrong namespace, so CloudWatch has no datapoints and the alarm sits in INSUFFICIENT_DATA forever. Enable detailed monitoring on the instances (or confirm the metric namespace matches), wait for datapoints to accumulate, and the alarms will evaluate. An alarm without data cannot fire.