CloudWatch Dashboard Review
Dashboards are billed per dashboard beyond the free allowance, and one nobody opens is a recurring charge for a view with no reader.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, fixed.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Delete the unused CloudWatch dashboard. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
After a guided review, where you confirm the change, ZopNight deletes the resource, then checks the change took.
- Applies to
- CloudWatch Dashboards on AWS
- The fix, by hand
- CloudWatch → Dashboards → the resource → review last-viewed timestamp (visible in Actions menu).
- Ask the dashboard's tag owner (or git-blame the IaC source) whether it's still actively monitored.
- If a duplicate of another dashboard, consolidate the unique widgets into the canonical one.
- If genuinely unused: Actions → Delete.
- CloudWatch dashboards are free below 3; cost-driven cleanup matters only when you have many.
ZopNight does this for you after a guided review.
- Category
- Orphaned resources. Resources no longer attached to anything that needs them, such as unattached volumes and unassigned IPs.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-094- Full reference
Related checks
See the orphaned resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.