Cross-account observability enabled for CloudWatch Internet Monitor
You can now set up cross-account observability for Amazon CloudWatch Internet Monitor, so that you can get read-only access to monitors from multiple accounts within an AWS Region. Deploying applications by using resources in separate accounts is a good practice, to establish security and billing boundaries between teams and reduce the impact of operational events. For example, when you set up cross-account observability for Internet Monitor, you can access and view performance and availability measurements generated by monitors in different AWS accounts.
You can now set up cross-account observability for Amazon CloudWatch Internet Monitor, so that you can get read-only access to monitors from multiple accounts within an AWS Region. Deploying applications by using resources in separate accounts is a good practice, to establish security and billing boundaries between teams and reduce the impact of operational events. For example, when you set up cross-account observability for Internet Monitor, you can access and view performance and availability measurements generated by monitors in different AWS accounts.
To get started with cross-account monitoring in Internet Monitor, you use Amazon CloudWatch Observability Access Manager (OAM) to set up one or more of your AWS accounts as a monitoring account. The monitoring account then has the ability to view data in source accounts that you configure.
To learn more, visit the Internet Monitor user guide documentation.