SYSTEM Cited by 1 source
Amazon CloudWatch Observability Access Manager (OAM)¶
What it is¶
Amazon CloudWatch Observability Access Manager (OAM) is AWS's native primitive for cross-account CloudWatch observability. A monitoring account can be linked to many source accounts so that logs, metrics, and traces from the source accounts are query-visible from the central monitoring account without moving the telemetry data.
Role in account-per-tenant platforms¶
At multi-thousand-account scale, per-account CloudWatch dashboards fragment operational visibility. OAM (shipped post-Dec 2022) is AWS's answer for centralising the read surface without re-copying data. ProGlove's 2026-02 post explicitly notes that OAM was not available when they built their platform:
"Amazon CloudWatch offers greatly improved cross-account observability features today than when we started, for example, the Observability Access Manager." (Source: sources/2026-02-25-aws-6000-accounts-three-people-one-platform)
This is the "we would have bought it if it existed" signal — it confirms OAM is the native AWS-idiomatic counterpart to ProGlove's own third-party telemetry-aggregation tier. For new platforms, OAM is the starting point before deciding whether custom / third-party aggregation is needed.
Stub page — full OAM internals (source/sink account roles, trust policies, pricing) out of scope.
Seen in¶
- sources/2026-02-25-aws-6000-accounts-three-people-one-platform — called out as the post-we-started AWS-native primitive for the problem patterns/central-telemetry-aggregation solves.