Skip to main content

Guidance for Managing Account Health Dashboards and Insights on AWS

Overview

This Guidance demonstrates how to analyze AWS Health events across multiple AWS accounts using natural language queries and generative business intelligence. Organizations managing thousands of AWS resources can transform operations and security monitoring at scale, transitioning from manual processing to automated analysis. This Guidance enables site reliability engineering (SRE) teams and leadership to gain quick, comprehensive insights into the health of their AWS environment through intuitive queries. This approach streamlines monitoring of service health, planned changes, and other critical AWS notifications, making it easier to maintain optimal performance and respond to potential issues proactively.

Benefits

Deploy a unified health monitoring system that automatically collects and consolidates AWS Health events from multiple accounts into an interactive, customizable dashboard. Gain comprehensive visibility into service health across your entire AWS environment.

Transform complex health data into actionable insights using Amazon Q's natural language capabilities. Quickly identify impacted resources by asking simple questions like "Show me impacted Lambda resources," enabling faster problem diagnosis and resolution.

Eliminate manual health event processing with a serverless pipeline that automatically collects, transforms, and visualizes AWS Health data in real time. Enable your technical teams to focus on innovation rather than monitoring.

How it works

These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.

Deploy with confidence

Ready to deploy? Review the sample code on GitHub for detailed deployment instructions to deploy as-is or customize to fit your needs. 

Go to sample code

Disclaimer

The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.

References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.