Operators want one CloudWatch dashboard that shows metrics from three accounts. They currently paste screenshots into chat. What should be configured?
Select an answer to reveal the explanation.
Short Explanation
A screenshot is a postcard of a graph. You want the graph itself, from all three accounts, on one dashboard. Cross-account observability is how CloudWatch does that, and peering networks does not merge metrics.
Full Explanation
CloudWatch cross-account observability lets a monitoring account discover and graph metrics, logs, and traces from source accounts. One dashboard can then include widgets from all three. Screenshots go stale and are not alarmable. CloudTrail does not draw metric graphs. VPC peering connects networks and does not share CloudWatch metrics. Caveat: each source account has to share with the monitoring account, and the operators still need permission to view the dashboard in that account. Operational check: a widget on the monitoring account's dashboard should show a live metric from each of the other two accounts without a screenshot. In the monitoring account, link the source accounts and grant the operators a role that can read metrics there. Each widget names the source account and Region. A trail in one account does not draw another account's CPU. Peering is irrelevant to the dashboard. After the link, change a metric in a source account and confirm the monitoring dashboard moves without anyone pasting an image.