> ## Documentation Index
> Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AWS Health and Personal Health Dashboards

> Overview of AWS Health and Personal Health Dashboard, EventBridge integration, notification targets, API access and support requirements, multi account aggregation, and best practices for automating incident detection and response

Welcome back. This lesson explains AWS Health and the Personal Health Dashboard — essential tools for incident detection, account-level visibility, and automated incident response on AWS. We cover event sources, dashboard differences, EventBridge integration patterns, notification targets, API access requirements, organization aggregation, permissions, monitoring, and best practices for automating response workflows.

![A presentation slide titled "AWS Health and Personal Health Dashboards" showing four informational cards: AWS Health Event Sources, Dashboard Types, EventBridge Integration, and Exam Focus. Each card contains a short description about event notifications, dashboard types, real-time event routing, and exam-relevant tasks.](https://mintcdn.com/kodekloud-c4ac6d9a/SSy1aL2mVSdeEi1p/images/AWS-Certified-DevOps-Engineer-Professional/Domain-5-Incident-and-Event-Response/AWS-Health-and-Personal-Health-Dashboards/aws-health-personal-dashboards-overview.jpg?fit=max\&auto=format\&n=SSy1aL2mVSdeEi1p\&q=85\&s=51b33201751f8b01b78a784e1eaa14be)

## What is AWS Health?

AWS Health surfaces AWS-initiated events that can impact AWS services and your resources. It provides:

* Visibility into service incidents, scheduled changes, and account-level notifications.
* Timelines and affected-resource context to help prioritize response.
* Integration with Amazon EventBridge for automated routing to remediation pipelines (for example: Lambda, Step Functions, SNS).

Note: AWS Health only receives AWS-initiated events — you cannot publish custom events into AWS Health.

![The slide titled "AWS Health" shows two magenta icons — "AWS Health Dashboard" (heart/ECG) and "Amazon EventBridge" (network/molecule) — with a plus sign between them. Below are three labeled boxes: "Real-Time Notifications," "Resource Impact," and "EventBridge Ready."](https://mintcdn.com/kodekloud-c4ac6d9a/SSy1aL2mVSdeEi1p/images/AWS-Certified-DevOps-Engineer-Professional/Domain-5-Incident-and-Event-Response/AWS-Health-and-Personal-Health-Dashboards/aws-health-dashboard-eventbridge-notifications.jpg?fit=max\&auto=format\&n=SSy1aL2mVSdeEi1p\&q=85\&s=3eb22671a33115dfc4cfea98dc7e90c4)

## Service Health Dashboard vs Personal Health Dashboard

* Service Health Dashboard (public): `https://status.aws.amazon.com` — global, service-level status visible to anyone.
* Personal Health Dashboard (account-specific): requires AWS sign-in; surfaces issues and scheduled changes that affect your account and resources.

| Dashboard | Scope | Access |
| - | -: | - |
| Service Health Dashboard | Global service status | Public (`https://status.aws.amazon.com`) |
| Personal Health Dashboard | Account-specific incidents, resource impact | Requires AWS authentication (console/API) |

![A slide comparing the AWS Service Health Dashboard and the Personal Health Dashboard, outlining each one’s scope, access, use cases, and URL/location. The Service Health Dashboard shows global public AWS service status (status.aws.amazon.com), while the Personal Health Dashboard shows account-specific resource impacts and requires AWS authentication.](https://mintcdn.com/kodekloud-c4ac6d9a/SSy1aL2mVSdeEi1p/images/AWS-Certified-DevOps-Engineer-Professional/Domain-5-Incident-and-Event-Response/AWS-Health-and-Personal-Health-Dashboards/aws-service-health-vs-personal-health.jpg?fit=max\&auto=format\&n=SSy1aL2mVSdeEi1p\&q=85\&s=78a29337357c85ad6c4f208bf6b1f20a)

## Event types and retention

Common event categories surfaced by AWS Health:

* Service events (incidents, outages)
* Scheduled changes (e.g., instance retirement, maintenance windows)
* Account notifications (quotas, limits, billing-impacting events)
* Announcements (product updates, feature rollouts)

Retention: the Personal Health Dashboard keeps up to 90 days of historical events for audit and analysis.

### Example event structure

Events share a consistent JSON schema with fields like `eventTypeCode`, `eventTypeCategory`, `service`, `region`, `startTime`, `endTime`, and `affectedEntities`. Example (simplified):

```json theme={null}
{
  "eventTypeCode": "AWS_EC2_INSTANCE_RETIREMENT_SCHEDULED",
  "eventTypeCategory": "scheduledChange",
  "service": "EC2",
  "region": "us-east-1",
  "startTime": "2024-03-15T10:00:00Z",
  "endTime": "2024-03-15T12:00:00Z",
  "affectedEntities": [
    {
      "entityValue": "i-0123456789abcdef0",
      "entityArn": "arn:aws:ec2:us-east-1:123456789012:instance/i-0123456789abcdef0"
    }
  ]
}
```

## EventBridge integration (real-time routing)

Amazon EventBridge automatically receives AWS Health events; you do not need to enable a separate forwarding setting. Events typically arrive within seconds and can be routed to many AWS targets for notification or remediation.

A typical EventBridge rule pattern that matches AWS Health events:

```json theme={null}
{
  "source": ["aws.health"],
  "detail-type": ["AWS Health Event"],
  "detail": {
    "service": ["EC2"],
    "eventTypeCategory": ["scheduledChange"],
    "eventTypeCode": ["AWS_EC2_INSTANCE_RETIREMENT_SCHEDULED"],
    "region": ["us-east-1"]
  }
}
```

You do not configure AWS Health to "send" events to EventBridge — the integration is automatic. Beware exam distractors claiming you must configure a separate send step.

## Notification targets and routing

EventBridge can route health events to many AWS services for notifications and automation:

* Lambda (custom remediation code)
* Amazon SNS (fan-out notifications, SMS via SNS)
* Amazon SQS (buffering, durable processing)
* Step Functions (coordinated multi-step runbooks)
* Systems Manager (OpsCenter, automation documents)
* S3 (archival of events for audit)

| Target | Use case |
| - | - |
| Lambda | Run custom remediation or enrichment |
| Amazon SNS | Push alerts (email/SMS/mobile push) |
| Step Functions | Orchestrate multi-step incident workflows |
| Systems Manager | Create OpsCenter tickets, run Automation documents |
| Amazon SQS | Queue events for async processing |
| Amazon S3 | Archive raw events for long-term retention |

![A presentation slide titled "Notification Capabilities" showing four colored feature boxes labeled Console Notifications, EventBridge Routing, OpsCenter Integration, and Multi-Account View. Each box has a brief explanation underneath and a footer note mentioning "No Native SMS" and copyright KodeKloud.](https://mintcdn.com/kodekloud-c4ac6d9a/SSy1aL2mVSdeEi1p/images/AWS-Certified-DevOps-Engineer-Professional/Domain-5-Incident-and-Event-Response/AWS-Health-and-Personal-Health-Dashboards/notification-capabilities-kodekloud-features.jpg?fit=max\&auto=format\&n=SSy1aL2mVSdeEi1p\&q=85\&s=1244c56e615a488e8cfd9d4c31d650e6)

## Common incident response use cases

* Proactive maintenance: handle instance retirement or scheduled host maintenance.
* Service disruption response: trigger failover, scale-out, or alternative routing.
* Security event response: rotate exposed credentials or quarantine resources.
* Capacity and quota planning: automate actions when limits change.
* Audit and compliance: archive events, correlate with CloudTrail and Config.

![A slide titled "Incident Response — Use Cases" showing four colored boxes: Proactive Maintenance, Service Disruption Response, Security Event Response, and Capacity Planning with brief descriptions of each (e.g., automates EC2 retirement, manages outages, rotates exposed credentials, monitors quotas). The slide is from KodeKloud and outlines common incident response scenarios.](https://mintcdn.com/kodekloud-c4ac6d9a/SSy1aL2mVSdeEi1p/images/AWS-Certified-DevOps-Engineer-Professional/Domain-5-Incident-and-Event-Response/AWS-Health-and-Personal-Health-Dashboards/incident-response-use-cases-kodekloud.jpg?fit=max\&auto=format\&n=SSy1aL2mVSdeEi1p\&q=85\&s=334453a37925461a98a646467d7b0fe6)

## API access and Support Plan requirements

Programmatic access to the AWS Health APIs (the APIs behind the Personal Health Dashboard) is gated by support plan:

* Basic: no AWS Health API access.
* Business: access to account-level Health APIs.
* Enterprise / Enterprise On-Ramp: access to account-level and organization-level Health APIs (aggregate across member accounts).

| Support plan | Account-level API | Organization-level API |
| - | :-: | :-: |
| Basic | No | No |
| Business | Yes | No |
| Enterprise / Enterprise On-Ramp | Yes | Yes |

![A slide titled "AWS Health API Access" that lists four API calls (DescribeEvents, DescribeEventDetails, DescribeAffectedEntities, DescribeEventsForOrganization) with short descriptions of their functions. A table on the right shows which AWS support plans include API access (Basic not available; Business and Enterprise included, with organization-level inclusion for enterprise options).](https://mintcdn.com/kodekloud-c4ac6d9a/SSy1aL2mVSdeEi1p/images/AWS-Certified-DevOps-Engineer-Professional/Domain-5-Incident-and-Event-Response/AWS-Health-and-Personal-Health-Dashboards/aws-health-api-access-support-plans.jpg?fit=max\&auto=format\&n=SSy1aL2mVSdeEi1p\&q=85\&s=c33f4a2c77c6c5bff85e730382d71d0e)

## Organizations integration and IAM permissions

To aggregate health events across multiple AWS accounts, enable AWS Organizations and grant the necessary IAM permissions to the roles or users used by your tooling. Key actions you may need:

```text theme={null}
health:DescribeEvents
health:DescribeEventDetails
health:DescribeAffectedEntities
health:DescribeEventsForOrganization
health:DescribeEventDetailsForOrganization
```

Always apply least privilege: scope actions and resources to the minimum required.

## EventBridge rule examples

Use targeted event patterns to reduce noise and only trigger workflows for relevant events.

Match any AWS Health event:

```json theme={null}
{
  "source": ["aws.health"]
}
```

Match all EC2 service events:

```json theme={null}
{
  "source": ["aws.health"],
  "detail": {
    "service": ["EC2"]
  }
}
```

Match scheduled changes only:

```json theme={null}
{
  "source": ["aws.health"],
  "detail": {
    "eventTypeCategory": ["scheduledChange"]
  }
}
```

Match a specific event type (EC2 instance retirement scheduled):

```json theme={null}
{
  "source": ["aws.health"],
  "detail": {
    "eventTypeCode": ["AWS_EC2_INSTANCE_RETIREMENT_SCHEDULED"]
  }
}
```

Match a specific service, category, and region:

```json theme={null}
{
  "source": ["aws.health"],
  "detail": {
    "service": ["RDS"],
    "eventTypeCategory": ["issue"],
    "region": ["us-east-1"]
  }
}
```

EventBridge targets commonly used for remediation include Lambda, SNS, Step Functions, Systems Manager, and SQS.

![A diagram titled "EventBridge Rule – Examples" showing Amazon EventBridge in the center routing to five AWS services. Icons and short descriptions for AWS Lambda, Amazon SNS, Amazon Step Functions, Amazon Systems Manager, and Amazon SQS are displayed.](https://mintcdn.com/kodekloud-c4ac6d9a/SSy1aL2mVSdeEi1p/images/AWS-Certified-DevOps-Engineer-Professional/Domain-5-Incident-and-Event-Response/AWS-Health-and-Personal-Health-Dashboards/eventbridge-rule-examples-aws-targets.jpg?fit=max\&auto=format\&n=SSy1aL2mVSdeEi1p\&q=85\&s=44b55000bacd2d0c679d3a1b5113130d)

## Permissions for multi-account aggregation

If building organization-level workflows, ensure the role or user includes the Health API actions necessary for aggregation and querying. Example actions to include in IAM policies:

```text theme={null}
health:DescribeEvents
health:DescribeEventDetails
health:DescribeAffectedEntities
health:DescribeEventsForOrganization
health:DescribeEventDetailsForOrganization
```

Scope the policy to the organization or accounts as appropriate to maintain least privilege.

## Monitoring, troubleshooting, and observability

* Monitor EventBridge rule metrics (invocations, successes, failures).
* Use CloudWatch Logs for Lambda and Step Functions to inspect processing.
* Archive raw events to S3 for long-term audit and offline analysis.
* Correlate Health events with CloudWatch metrics, CloudTrail, and AWS X-Ray traces where applicable.
* Use the Personal Health Dashboard’s 90-day history to provide operational context during incident reviews.

## Best practices and recommended architecture

* Enable the organizational view in the Personal Health Dashboard when managing multiple accounts.
* Create narrow EventBridge rules to reduce alert noise and downstream costs.
* Filter SNS topics and use subscription filters to control who receives alerts.
* Archive events to S3 and/or push to a data lake for compliance and post-incident analysis.
* Test automation workflows (Lambda, Step Functions, Systems Manager documents) regularly in non-production before enabling production triggers.

Example pipeline architecture:
Health events → EventBridge → Lambda (enrichment) → Step Functions (orchestration) → SNS + Systems Manager (notifications & OpsCenter) → S3 (archival).

![A "Best Practices" slide showing an AWS event-driven architecture. It diagrams a pipeline from a Health Event through EventBridge, Lambda, Step Functions, SNS, and Systems Manager to S3 for archival, with recommended practices listed above.](https://mintcdn.com/kodekloud-c4ac6d9a/SSy1aL2mVSdeEi1p/images/AWS-Certified-DevOps-Engineer-Professional/Domain-5-Incident-and-Event-Response/AWS-Health-and-Personal-Health-Dashboards/aws-event-driven-architecture-best-practices.jpg?fit=max\&auto=format\&n=SSy1aL2mVSdeEi1p\&q=85\&s=cd7a17bb298b10ea08c3511d39ebb2f3)

## Integrations with other AWS services

AWS Health events are frequently ingested or correlated with:

* Systems Manager OpsCenter (create tickets, attach runbooks)
* Security Hub (correlate security findings)
* CloudWatch (generate custom metrics and alarms)
* Service Catalog (block or gate deployments based on health signals)
* Cost Explorer (assess cost impact during incidents)

![A presentation slide titled "Integration With Other AWS Services" showing five colored boxes for Systems Manager OpsCenter, Security Hub, CloudWatch, Service Catalog, and Cost Explorer, each with a short description of how they integrate. The slide outlines how these services ingest, correlate, and act on health and security events for monitoring, remediation, and cost analysis.](https://mintcdn.com/kodekloud-c4ac6d9a/SSy1aL2mVSdeEi1p/images/AWS-Certified-DevOps-Engineer-Professional/Domain-5-Incident-and-Event-Response/AWS-Health-and-Personal-Health-Dashboards/aws-service-integration-monitoring-remediation-cost.jpg?fit=max\&auto=format\&n=SSy1aL2mVSdeEi1p\&q=85\&s=1e3561226cf49d754ce4d3cb1257f477)

## How AWS Health fits in the monitoring ecosystem

* AWS Health: AWS-initiated events and account-specific resource impacts.
* Amazon CloudWatch: Metrics, logs, alarms, operational monitoring for workloads.
* AWS CloudTrail: API call history for auditing and forensics.
* AWS Config: Configuration drift and compliance checks.

Use the right tool for each concern and integrate them to build a comprehensive incident detection and response strategy.

![A slide containing a comparison table of AWS monitoring services. It lists AWS Health, CloudWatch, CloudTrail, and AWS Config with columns for Purpose, Data Source, Use When, and limitations ("Cannot").](https://mintcdn.com/kodekloud-c4ac6d9a/SSy1aL2mVSdeEi1p/images/AWS-Certified-DevOps-Engineer-Professional/Domain-5-Incident-and-Event-Response/AWS-Health-and-Personal-Health-Dashboards/aws-monitoring-services-comparison-table.jpg?fit=max\&auto=format\&n=SSy1aL2mVSdeEi1p\&q=85\&s=2e7cd5bbd4197caac0b2be296215f6c1)

For both the exam and production designs: remember that AWS Health provides AWS-initiated events, integrates with EventBridge automatically, and that API access requires Business or Enterprise support (organization-level APIs typically require Enterprise). Be ready to design focused EventBridge rules and end-to-end automation (Lambda, Step Functions, Systems Manager) that respond to these events.

Thanks for reading.

> **[Watch Video](https://learn.kodekloud.com/user/courses/aws-certified-devops-engineer-professional/module/0054c8f3-16fd-4414-be5f-d43fc173b566/lesson/7d45354a-4b11-4a97-b7b5-d3a197f11a20)**


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.