AWS Personal Health Dashboard: What It Is and When to Use It
Definition
The AWS Personal Health Dashboard (PHD) provides a personalized view of the health of AWS services and resources that you are using. It alerts you to and provides remediation guidance for AWS events that might affect your specific accounts and workloads, such as service degradations, scheduled maintenance, or account notifications. As of 2022, the classic Personal Health Dashboard and the public Service Health Dashboard have been unified into a single experience called the AWS Health Dashboard, where the personalized, authenticated view retains the functionality of the original PHD.
How It Works
The AWS Health Dashboard functions as a targeted information radiator for events related to your AWS environment. When an internal AWS monitoring system detects an issue, plans maintenance, or needs to send an account-specific notification, it generates a health event. These events are then filtered and displayed specifically to the customers whose resources or accounts are affected.
Upon logging into the AWS Management Console, you are automatically presented with events relevant to you. The dashboard is organized into two primary views:
- Your account health: This is the personalized view showing events that directly impact your AWS account. It includes open and recent issues, scheduled changes, and other notifications, with an event log that retains all events for the past 90 days.
- Your organization health: If you use AWS Organizations, you can enable an aggregated view. This allows a central management or delegated administrator account to see all health events for every account within the organization, providing a comprehensive overview for large enterprises.
For automation, the AWS Health Dashboard is deeply integrated with Amazon EventBridge. You can create rules in EventBridge that match specific types of health events (e.g., an upcoming Amazon EC2 instance retirement). These rules can then trigger targets like AWS Lambda functions for automated remediation, Amazon Simple Notification Service (SNS) topics to alert on-call engineers, or integrations with third-party IT management tools.
Programmatic access is available via the AWS Health API, which allows you to pull health event data into custom dashboards or external monitoring systems. However, using the API requires an AWS Business, Enterprise On-Ramp, or Enterprise Support plan.
Key Features and Limits
- Personalized View: Unlike the public Service Health Dashboard, which shows the general status of services, the Personal Health Dashboard shows only the events known to affect your specific resources and services.
- Proactive Notifications: Get advance warning for scheduled activities like hardware maintenance, software patches, or instance retirements, allowing you to plan accordingly.
- Organizational View: Aggregate health events from all accounts in an AWS Organization into a single dashboard in the management account. This feature is available at no additional cost and does not require a premium support plan for the dashboard view.
- Automation with Amazon EventBridge: Natively integrates with EventBridge, allowing you to build event-driven workflows to automatically respond to health events. This is the primary method for creating custom alerts and automated actions.
- Detailed Troubleshooting Guidance: Events include detailed descriptions and actionable guidance to help you diagnose and resolve issues quickly. For example, an alert about a degraded Amazon EBS volume might include a list of affected resources and links to documentation on restoring from a snapshot.
- AWS Health API: Provides programmatic access to health events for integration with external systems. Access to the Health API is restricted to accounts with an AWS Business, Enterprise On-Ramp, or Enterprise Support plan.
- Event History: The dashboard maintains a log of all health events affecting your account for the past 90 days.
- Fine-Grained Access Control: You can use AWS Identity and Access Management (IAM) policies to control which users or roles can view specific types of events, allowing you to restrict access to sensitive notifications (e.g., security alerts).
Common Use Cases
- Incident Response and Root Cause Analysis: When an application experiences issues, the Personal Health Dashboard is often the first place to check to determine if an underlying AWS service issue is the cause, which can significantly reduce Mean Time To Detection (MTTD).
- Proactive Operations Management: An operations team can use notifications about upcoming EC2 instance retirements to proactively migrate applications to new instances before the maintenance window, avoiding downtime.
- Automated Remediation: Configure an EventBridge rule to detect an event for an EC2 instance in a degraded hardware region. This rule can trigger a Lambda function that automatically stops the instance, takes a final snapshot, and launches a replacement in a healthy Availability Zone.
- Centralized Multi-Account Monitoring: A central cloud operations team can use the Organizational View to monitor for impactful events across hundreds of development, staging, and production accounts from a single, aggregated dashboard.
- Security and Compliance Reporting: Security teams can track and audit security-related notifications from AWS. The 90-day event history can be used to generate reports for compliance audits.
Pricing Model
The AWS Health Dashboard console view is available to all AWS customers at no additional charge.
Costs may be incurred in two specific ways:
- AWS Health API Access: Programmatic access to the AWS Health API requires an active AWS Business Support, Enterprise On-Ramp, or Enterprise Support plan. If you do not have one of these plans, API calls will result in an error.
- Downstream Service Usage: While the health events themselves are free, you will pay for any AWS services you use to act on them. For example, if you configure an EventBridge rule to send a notification to an SNS topic, you will incur standard charges for SNS. If the rule triggers a Lambda function, you will pay for the Lambda execution time.
For detailed pricing of related services, refer to the AWS Pricing Calculator.
Pros and Cons
Pros:
- High Signal-to-Noise Ratio: Events are personalized, meaning you only see issues that are relevant to your specific resources, reducing alert fatigue.
- Proactive and Actionable: Provides advance notice for many types of maintenance and includes specific guidance for remediation.
- Deep Integration: Native integration with EventBridge and AWS Organizations makes it a powerful tool for automation and centralized governance.
- No Direct Cost: The dashboard itself is a free tool available to all AWS accounts.
- Centralized Visibility: The Organizational View is essential for managing large, multi-account environments effectively.
Cons:
- API Requires Paid Support: The inability to access the AWS Health API without a costly Business or Enterprise support plan is a significant limitation for smaller organizations that want to build custom integrations.
- Not a Performance Monitoring Tool: It reports on the health of the underlying AWS infrastructure, not the performance of your application code or resource-level metrics like CPU utilization. For that, you need Amazon CloudWatch.
- Limited Event History: The 90-day event history may not be sufficient for long-term forensic analysis or compliance requirements, necessitating a solution to export and store events long-term.
Comparison with Alternatives
AWS Personal Health Dashboard vs. AWS Service Health Dashboard
- Scope: The Personal Health Dashboard is a personalized, authenticated view of events affecting your resources. The Service Health Dashboard is a public, unauthenticated page showing the general status of all AWS services in all regions.
- Purpose: Use the PHD to answer, "Is an AWS issue affecting my application?" Use the public Service Health Dashboard to answer the general question, "Is Amazon S3 having a problem in us-east-1?"
AWS Personal Health Dashboard vs. Amazon CloudWatch
- Focus: The PHD focuses on the health of the underlying AWS platform and services. CloudWatch focuses on the performance and operational health of your resources running on that platform (e.g., EC2 CPU, Lambda errors, application logs).
- Data Source: PHD events are generated by AWS service teams. CloudWatch metrics and logs are generated by your resources and applications.
- Relationship: They are complementary. An alert in the PHD (e.g., "EC2 network connectivity issues") can explain why you are seeing alarms in CloudWatch (e.g., "High target connection error count" in a load balancer).
Exam Relevance
The AWS Health Dashboard is a key operational tool and is relevant for several AWS certifications:
- AWS Certified Cloud Practitioner (CLF-C02): Candidates should understand the fundamental difference between the personalized Personal Health Dashboard and the public Service Health Dashboard.
- AWS Certified Solutions Architect - Associate (SAA-C03): Architects should know how the PHD provides crucial information for designing resilient and highly available systems, especially regarding scheduled maintenance and service-wide events.
- AWS Certified SysOps Administrator - Associate (SOA-C02): This certification covers the PHD in the most depth. Candidates are expected to know how to interpret events, configure alerts using Amazon EventBridge and SNS, and understand the benefits of the Organizational View for centralized monitoring.
Frequently Asked Questions
Q: What is the difference between the AWS Personal Health Dashboard and the AWS Service Health Dashboard?
A: The AWS Personal Health Dashboard provides a personalized view of AWS service events that directly affect your specific resources and account. The AWS Service Health Dashboard is a public page that shows the general status of all AWS services across all regions, regardless of whether you use them.
Q: How can I get automated alerts from the AWS Personal Health Dashboard?
A: The primary method for automation is to use Amazon EventBridge. You can create rules in EventBridge that match specific health events and then send them to a target, such as an Amazon SNS topic to send an email or SMS, an AWS Lambda function to perform a custom action, or third-party services like Slack or PagerDuty.
Q: Can I see health events for all accounts in my AWS Organization in one place?
A: Yes. You can enable the "Organizational View" feature from your AWS Organizations management account. This aggregates all health events from your member accounts into a single, centralized dashboard, providing a complete overview of your organization's operational health.
This article reflects AWS features and pricing as of 2026. AWS services evolve rapidly — always verify against the official AWS documentation before making production decisions.