# Amazon CloudWatch Dashboard

> CloudWatch dashboards bill per dashboard per month once an account passes the free tier of 3. Dashboards outlive their creators and services, adding small permanent charges. ZopNight discovers every dashboard on the 6-hour cycle, attributes cost from Cost Explorer or CUR 2.0, and recommends deleting the unused ones.

Source: https://zop.dev/integrations/aws/cloudwatch-dashboard
Updated: 2026-08-19

---

A CloudWatch dashboard displays metric visualizations, billed per dashboard per month beyond the free tier. Dashboards outlive the teams and services that created them, adding small but permanent charges.

## The per-dashboard meter and its free floor

CloudWatch includes 3 dashboards (with up to 50 metrics) free per account; beyond that, each dashboard bills a flat monthly fee regardless of how often anyone opens it. A dashboard is pure configuration (it stores queries, not data), so its cost has no relationship to the metric volume it displays. The math only matters at population scale: accounts accumulate dashboards the way wikis accumulate pages, and a hundred of them is a permanent monthly charge for what is mostly archaeology.

## Inventory over an unglamorous resource

ZopNight discovers dashboards through a dedicated provider on the 6-hour cycle and attributes their cost from Cost Explorer or CUR 2.0. The recommendation is straightforward cleanup: dashboards whose widgets reference deleted resources, duplicate whose-service-is-down boards from reorganized teams, and boards untouched since their creating project shipped. Because a dashboard holds no data, deletion loses only layout and every underlying metric remains queryable, which makes this one of the lowest-risk cleanups in the account.

## How dashboard graveyards form

Every incident spawns a dashboard; few incidents end with its deletion. Infrastructure-as-code multiplies boards per environment: dev, staging, prod copies of the same layout, two of which nobody views. Team reorganizations strand boards under naming conventions no current team recognizes. And observability migrations leave the CloudWatch generation behind as a shadow of the Grafana or Datadog boards that replaced them.

## Pruning from the dashboards list

The CloudWatch console's Dashboards view lists every board with its last-modified time, which is an adequate staleness proxy. A quick open of anything untouched for a year settles it: widgets full of no-data panes mean the underlying resources are gone, and the board can follow them.