2.1.3. CloudWatch Dashboards (Multi-Account, Multi-Region)
💡 First Principle: A dashboard is an operational control panel — it surfaces the metrics that matter most for a specific context, so you don't have to search for them under pressure. Good dashboards tell you the health story at a glance; bad dashboards show everything and help you understand nothing.
CloudWatch Dashboards support both cross-account and cross-region metrics on a single dashboard. This is critical in enterprise environments where your application may span multiple AWS accounts and regions. You configure cross-account dashboards by enabling sharing in the source account and granting access in the monitoring account. The fuller option is CloudWatch cross-account observability: designate a monitoring account and link source accounts to it (one by one, or every account in an AWS Organization). Linked accounts share metrics, logs and traces, so the monitoring account can query them and build dashboards and alarms without switching roles. Links are set up per Region.
Widget Types Available:
| Widget | Best For |
|---|---|
| Metric | Time-series graphs of one or more metrics |
| Alarm Status | Quick health overview (green/red for each alarm) |
| Log Insights Query | Embedded log analysis results |
| Text | Labels, instructions, links |
| Explorer | Dynamic metric browsing by tag/resource type; a tag-filtered Explorer widget picks up new resources and drops terminated ones automatically, so it suits Auto Scaling fleets |
Shareable Dashboards allow you to share a dashboard as a public URL without requiring the viewer to have an AWS account. This is useful for sharing NOC dashboards with stakeholders who aren't AWS users. The shared URL provides read-only access to the dashboard.
A widget with no data usually means the metric has no datapoints in the selected time range: the resource wasn't emitting yet, or a redeploy changed the dimension value (such as an instance ID) the widget points at.
⚠️ Exam Trap: When a question asks about multi-account monitoring visibility, the answer is CloudWatch cross-account dashboards or CloudWatch cross-account observability (not a separate third-party tool). For cross-region visibility in a single pane, dashboards can aggregate metrics from any region you specify.
Reflection Question: Your company has 5 AWS accounts (dev, staging, prod, logging, security). Which account should host the centralized CloudWatch dashboard, and how do the other accounts grant it access?
