Amazon CloudWatch Container Insights launches cross-account observability across Amazon Elastic Kubernetes Service (EKS) to help you monitor and troubleshoot applications that span across multiple AWS accounts within an AWS Region. Central Operational Teams managing container administration can now monitor and analyze container health and performance across their organization from a consolidated view and maintain the overall application health status to achieve the best business results.

Using cross-account observability in Container Insights for EKS, you do not need to switch accounts when you are troubleshooting, which saves you time and effort. With cross-account observability you can now filter your containers operating at high utilization by account ids or account labels and identify which teams require rightsizing in their resources. Cross-account observability enables you to drill down into an alarm on your containers regardless of the account owning the resource and identify the root-cause without account boundaries, reducing your mean time to resolution.

Once you enable cross account observability for CloudWatch, it works with Container Insights for EKS out-of-the-box. After you complete the set up, you can use your monitoring accounts to access organization-wide container observability in Container Insights for EKS.

Cross-account observability in Container Insights for EKS is now available in all public AWS Regions, including the AWS GovCloud (US) Regions and China (Beijing, operated by Sinnet), and China (Ningxia, operated by NWCD). Cross-account observability for Container Insights comes with no extra cost - see the Amazon CloudWatch pricing page for details. To learn more about cross-account observability, see the Container Insights documentation.