Cargando...
Cargando...
Real-time visibility into AWS service health, planned maintenance, and account-specific impact — not metrics, not costs, not remediation.
AWS Health Dashboard provides personalized, real-time alerts and historical information about AWS service health events that may affect your specific account and resources. It surfaces two types of visibility: the global Service Health Dashboard (public, showing all AWS service status) and the Personal Health Dashboard / AWS Health (account-specific, showing only events relevant to your resources). It integrates natively with Amazon EventBridge to enable automated workflows in response to health events, and with AWS Organizations for enterprise-wide health visibility.
To proactively notify AWS customers of service disruptions, scheduled maintenance, and account-specific issues that may impact their workloads, enabling faster incident response and change management.
Use When
Avoid When
Personal Health Dashboard (account-specific events)
Shows only events relevant to your account's resources — far more actionable than the public dashboard
Service Health Dashboard (global public view)
Public, no login required; shows broad AWS service status by region at status.aws.amazon.com
AWS Health API
Requires Business, Enterprise On-Ramp, or Enterprise Support; enables programmatic event retrieval
Amazon EventBridge integration (native)
Health events automatically appear as events in EventBridge under the 'aws.health' event source — no configuration required to start receiving them
AWS Organizations integration (Organizational View)
Aggregates health events across all accounts; must be explicitly enabled on management account with Business+ Support
Proactive notifications for scheduled maintenance
Advance notice for EC2 host retirements, RDS maintenance, certificate expirations, and more
Event filtering by service, region, or resource ARN
API and EventBridge rules can filter on specific services, event type categories, or affected resource ARNs
Automated remediation
Health Dashboard surfaces events only — remediation requires pairing with EventBridge + Lambda, SSM Automation, or Step Functions
CloudWatch metrics from Health
Health Dashboard does not publish CloudWatch metrics; it is an event-driven service, not a metrics service
90-day event history
Viewable in console and via API; for longer retention, export via EventBridge to S3 or a SIEM
SNS notifications (direct)
Health does not natively push to SNS directly; route through EventBridge rule → SNS topic for notifications
AWS CloudTrail logging of Health API calls
All AWS Health API calls are logged in CloudTrail for audit and compliance purposes
Automated Remediation on Health Events
high freqAWS Health emits events to EventBridge under the 'aws.health' source. An EventBridge rule filters for specific event types (e.g., AWS_EC2_INSTANCE_RETIREMENT_SCHEDULED) and triggers a Lambda function to automatically stop, snapshot, or migrate the affected instance. This is the canonical exam pattern for automated response to infrastructure health events.
Ops Team Health Alerting
high freqEventBridge rule matches aws.health events and routes to an SNS topic, sending email or SMS to on-call engineers. Simpler than Lambda-based automation; used when human intervention is required rather than automated remediation.
Enterprise-Wide Health Aggregation
high freqWith Organizational View enabled on the management account (requiring Business+ Support), health events from all member accounts are visible centrally. EventBridge in the management account can then route any member account's health event to a centralized SIEM, ticketing system, or Slack channel.
Complementary Monitoring Stack (NOT the same thing)
high freqCloudWatch monitors metrics, logs, and application behavior that YOU generate. AWS Health monitors AWS infrastructure events that AWS generates about your resources. They solve different problems and must both be present in a complete monitoring architecture. Exam questions often test whether candidates know which tool answers which question.
Health API Audit Trail
medium freqAll calls to the AWS Health API (DescribeEvents, DescribeEventDetails, DescribeAffectedResources) are logged in CloudTrail. Used for compliance auditing to prove which users or roles queried health data and when.
Holistic Operational Intelligence
medium freqTrusted Advisor provides proactive best-practice recommendations (cost, security, performance, fault tolerance), while AWS Health provides reactive and scheduled event notifications. Together they form a complete operational awareness layer. They are complementary, not redundant.
Self-Healing Infrastructure
medium freqEventBridge captures an EC2 retirement or EBS degradation health event and triggers an SSM Automation runbook to replace the instance or reattach the volume — no human intervention required. This pattern is tested in DevOps Professional scenarios.
AWS Health API requires Business, Enterprise On-Ramp, or Enterprise Support — Basic and Developer plans get the console UI only. Any exam scenario asking about programmatic/automated health event processing implies at minimum Business Support.
AWS Health Dashboard does NOT perform automated remediation. When a question asks how to automatically respond to a health event (e.g., retire an EC2 instance), the correct architecture is: AWS Health → EventBridge → Lambda (or SSM Automation). Health alone does nothing automatically.
The EventBridge event source for AWS Health is 'aws.health'. This is a native, zero-configuration integration — events flow automatically. You only need to create EventBridge rules to act on them. Knowing this event source name can appear in scenario-based questions.
AWS Health Dashboard NEVER performs automated remediation. The correct architecture for automated response is always: Health event → EventBridge → Lambda or SSM Automation.
Health API requires Business Support or higher. Any exam scenario involving programmatic or automated health event processing implies this prerequisite — if a Basic/Developer account is described, the API is not available.
'Personalized' or 'account-specific' health events = AWS Health (Personal Health Dashboard). General AWS service status visible to all = public Service Health Dashboard at status.aws.amazon.com. Never confuse these two.
Organizational View must be explicitly enabled — it is NOT on by default even when AWS Organizations is configured. The management account needs Business+ Support. Member accounts do NOT each need paid support for their events to appear in the org-level view.
AWS Health event data is retained for 90 days. For compliance or post-incident reviews requiring longer retention, the architecture is: EventBridge rule → Kinesis Data Firehose → S3. This is a common SAP-C02 and DOP-C02 architecture question.
The public Service Health Dashboard (status.aws.amazon.com) shows general AWS service status for all customers. It does NOT show account-specific impact. If a question mentions 'personalized', 'account-specific', or 'my resources', the answer is AWS Health / Personal Health Dashboard, not the public status page.
AWS Health does NOT publish CloudWatch metrics. You cannot create a CloudWatch alarm directly on a health event. The correct integration path for alerting is Health → EventBridge → SNS, not Health → CloudWatch → SNS.
For the CLF-C02, focus on the conceptual difference: AWS Health Dashboard tells you about AWS infrastructure problems affecting your account. CloudWatch tells you about your application and resource performance. Cost Explorer tells you about spending. These three are frequently confused in foundational-level questions.
AWS Trusted Advisor and AWS Health are frequently paired in exam questions but serve distinct purposes: Trusted Advisor = proactive best-practice recommendations (what you SHOULD do); Health = reactive event notifications (what IS happening to your AWS infrastructure). Neither replaces the other.
Common Mistake
AWS Health Dashboard can be used to monitor application performance and detect when my application is slow or down.
Correct
AWS Health Dashboard only surfaces events generated by AWS about AWS infrastructure — it has zero visibility into your application layer, custom metrics, or response times. For application performance monitoring, use Amazon CloudWatch (metrics, alarms, logs), AWS X-Ray (tracing), or Amazon CloudWatch Application Insights.
This is the most common trap. Exam questions describe an application issue and ask which service to use. If the issue is AWS infrastructure (e.g., EC2 host degradation), Health Dashboard is relevant. If the issue is application behavior (e.g., high latency, error rates), CloudWatch or X-Ray is the answer. The keyword 'application performance' always points away from Health Dashboard.
Common Mistake
AWS Health Dashboard automatically fixes problems — for example, it will automatically migrate an EC2 instance scheduled for retirement.
Correct
AWS Health Dashboard is a passive notification service only. It alerts you to events but takes no action. Automated remediation requires building an event-driven pipeline: AWS Health event → Amazon EventBridge rule → AWS Lambda or SSM Automation to perform the actual remediation.
Exam questions testing this misconception describe a scenario where you 'want to automatically respond to EC2 retirement notices' and offer AWS Health alone as a distractor. The correct answer always includes EventBridge + Lambda or SSM. Remember: Health = awareness, not action.
Common Mistake
AWS Health Dashboard helps optimize costs and identifies where I'm overspending on AWS services.
Correct
AWS Health Dashboard has no cost optimization functionality whatsoever. For cost optimization, use AWS Cost Explorer (spending analysis), AWS Budgets (spend alerts), AWS Trusted Advisor (cost-saving recommendations), or AWS Compute Optimizer (right-sizing). Health Dashboard is categorized under 'monitoring' not 'billing'.
In the SAA-C03 exam, Health Dashboard appears in the 'Design Cost-Optimized Architectures' domain context but is NOT itself a cost tool — it appears because understanding which monitoring tool to use is part of architecting efficiently. Candidates who see 'Health Dashboard' in a cost-optimization question context assume it's a cost tool. It is not.
Common Mistake
The public Service Health Dashboard and the Personal Health Dashboard (AWS Health) show the same information — just with different interfaces.
Correct
They show fundamentally different data. The public Service Health Dashboard (status.aws.amazon.com) shows broad AWS service status visible to all customers globally — it does NOT know about your specific resources. AWS Health / Personal Health Dashboard shows only events that affect YOUR specific account and resources. A service can show 'green' on the public dashboard while your specific account is impacted by an issue, or vice versa.
This distinction is heavily tested. The key differentiator word in exam questions is 'personalized' or 'account-specific' — these always map to AWS Health (Personal Health Dashboard), never to the public status page.
Common Mistake
Any AWS account can use the AWS Health API to build automated integrations with health events.
Correct
The AWS Health API is only available to accounts with Business, Enterprise On-Ramp, or Enterprise Support plans. Accounts on Basic or Developer support can view the Personal Health Dashboard in the console but cannot query it programmatically. This is a hard gate — no workaround exists.
Exam scenarios describe building an automation pipeline using the Health API and then ask what prerequisite is needed. The answer is Business Support or higher — not IAM permissions, not enabling a feature, but upgrading the support plan. This trips up candidates who assume all AWS APIs are universally available.
Common Mistake
AWS Health Dashboard analyzes network traffic and can detect network-level issues like DDoS attacks or unusual traffic patterns.
Correct
AWS Health Dashboard has no network traffic analysis capability. For network-level threat detection, use Amazon GuardDuty (threat detection), AWS Shield (DDoS protection), VPC Flow Logs (traffic logging), or AWS Network Firewall (traffic inspection). Health Dashboard only reports on AWS infrastructure health events that AWS itself has identified.
This misconception appears in security-focused exam questions. The trap is that a network issue (e.g., connectivity problems in a region) might appear in Health Dashboard as an AWS infrastructure event — but Health Dashboard itself does not analyze traffic. It merely reports that AWS has detected an infrastructure problem.
HEALTH = 'Heads-up Events About Life of Things in your Hosted-environment' — it's a notification service, not a fixer, not a metrics tool, not a cost tool.
Remember the two dashboards with 'PUBLIC vs. PERSONAL': Public (status.aws.amazon.com) = everyone sees the same thing; Personal (AWS Health) = only YOUR account's events. Personalized = Personal Health Dashboard.
For automation: H-E-L — Health fires the event → EventBridge catches it → Lambda (or SSM) fixes it. Health alone does nothing.
Support tier gate: 'Business Builds Bots' — Business Support is the minimum to use the Health API for automation/bots. Basic and Developer = console only.
CertAI Tutor · SAA-C03, SAP-C02, CLF-C02, DOP-C02 · 2026-03-07
In the Same Category
Comparisons
Guides & Patterns