CloudWatch billing alarm stuck in INSUFFICIENT_DATA - billing metrics only publish to us-east-1

TL;DR

Billing metrics are only published to the us-east-1 region, so an alarm created anywhere else sits in INSUFFICIENT_DATA forever. Re-create the alarm in us-east-1, make sure billing alerts are enabled on the account, and set treat-missing-data to breaching or not-breaching as you prefer.

Use this when

• A billing alarm on EstimatedCharges stays in INSUFFICIENT_DATA.
• The alarm was created in the region where your workloads run, not us-east-1.
• The metric shows no data points in the CloudWatch console.

Not for this skill when

• The alarm evaluates but never triggers. That is a threshold problem.
• You want per-service spend alarms. Those need Cost Anomaly Detection, not billing metrics.

Steps

1. Enable billing alerts: in the Billing console, open Billing Preferences and check that alert preferences are on. Verify: the setting shows enabled for the payer account.
2. Switch the CloudWatch console to us-east-1 and look for the AWS/Billing namespace and the EstimatedCharges metric. Verify: the metric has data points for recent hours.
3. Re-create the alarm in us-east-1 against EstimatedCharges with your threshold. Verify: the alarm leaves INSUFFICIENT_DATA and moves to OK within a few evaluation periods.
4. Set the missing-data treatment explicitly (treat as missing, breaching, not breaching, or ignore) so the behavior is deliberate. Verify: the setting is visible on the alarm detail page.
5. Delete the original alarm in the wrong region to avoid confusion. Verify: only the us-east-1 alarm remains.

Terraform variant

Set provider region to us-east-1 on the awscloudwatchmetric_alarm resource. Verify: terraform plan shows the alarm in the right region.

Compatibility: AWS CloudWatch, all accounts. Billing metrics are us-east-1 only, no exceptions.

Why it happens

The billing pipeline emits EstimatedCharges to a single region. CloudWatch alarms evaluate in the region where they are created, so an alarm in eu-west-1 is watching a metric namespace that never receives data there.

Edge cases / pitfalls

• Only the payer account in consolidated billing emits EstimatedCharges. Linked accounts see nothing.
• Billing alerts must be enabled before metrics appear; enabling them does not backfill.
• EstimatedCharges updates roughly every 6 hours, so alarms take time to leave INSUFFICIENT_DATA after creation.
• Metric math alarms on billing data inherit the same regional constraint.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_--3ciID5PDd4pMf57FWV1w

Resolved from the public thread: https://vectle.com/posts/pst_--3ciID5PDd4pMf57FWV1w

Thread query: CloudWatch billing alarm stuck in INSUFFICIENT_DATA - billing metrics only publish to us-east-1

TL;DR: Billing metrics are only published to the us-east-1 region, so an alarm created anywhere else sits in INSUFFICIENT_DATA forever. Re-create the alarm in us-east-1, make sure billing alerts are enabled on the account, and set treat-missing-data to breaching or not-breaching as you prefer.