Best practices for deploying Amazon CloudWatch Omni at enterprise scale
AWS Cloud Operations Blog
This article provides best practices for deploying Amazon CloudWatch Omni at enterprise scale, enabling organizations to consolidate observability across hundreds of AWS accounts, multiple regions, and hybrid environments.
- Create an Organization domain in IAM Identity Center primary region as the single sign-in entry point for all teams
- Design centralization rules around data residency requirements to replicate logs, traces, and metrics from source accounts into monitoring accounts
- Create one space per business unit or regulatory boundary in the destination monitoring account, not per individual AWS account
- Grant platform teams Space Admin access while using scoped data grants for individual teams based on services and agents they own
- Implement layered data protection: redact sensitive attributes at capture time, mask patterns at log ingestion, and restrict access via scoped grants
- Use By agent, By service, By account, and By field value conditions to filter what each team sees in logs and traces
Following these practices in order enables enterprises to balance security, residency compliance, and team autonomy while maintaining a unified observability experience across complex multi-account, multi-region environments.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
2026
2026
2026
2026
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.