2 years ago

https://aws.amazon.com/polly/ Deploying applications using multiple AWS accounts is a good practice to establish security and billing boundaries between teams and reduce the impact of operational events. To give you the flexibility to monitor all the components of your applications from a centralized view, we are introducing today https://aws.amazon.com/cloudwatch/ cross-account observability, a new capability to search, analyze, and correlate cross-account telemetry data stored in CloudWatch such as metrics, logs, and traces.

Configuring CloudWatch Cross-Account Observability To enable cross-account observability, CloudWatch has introduced the concept of monitoring and source accounts: A monitoring account is a central AWS account that can view and interact with observability data shared by other accounts. A source account is an individual AWS account that shares observability data and resources with one or more monitoring accounts.

Using CloudWatch Cross-Account Observability To see how things work with cross-account observability, I deploy a simple cross-account application using two https://aws.amazon.com/lambda/ functions, one in the source account (multi-account-function-a) and one in the monitoring account (multi-account-function-b).