- Newest
- Most votes
- Most comments
OAM sinks and links operate strictly on a per-Region basis. The official AWS troubleshooting guide (Knowledge Center) "Troubleshoot cross account observability in CloudWatch | AWS re:Post" addresses a scenario exactly like yours.
Note: Cross-account observability links are Region specific. The source account link and the monitoring account sink must be in the same Region.
Furthermore, the official documentation "CloudWatch cross-account observability - Amazon CloudWatch" explicitly states the following:
A sink is a resource that represents an attachment point in a monitoring account. Source accounts can link to the sink to share observability data. Each account can have one sink per Region.
In other words, the specification confirms your conclusion: the location of the dashboard itself is irrelevant; what matters is having a sink-link pair corresponding to the Region where the metrics are actually emitted (which is always us-east-1 for CloudFront).
There is no other way than to deploy an additional sink-link pair specifically for us-east-1.
answered 22 days ago
Relevant content
asked 3 years ago
