# Getting started with your AWS Health Dashboard
You can use your AWS Health Dashboard to learn about AWS Health events. These events can affect your AWS services or AWS account. After you sign in to your account, the AWS Health Dashboard shows information in the following ways:
+ **[Your account events](aws-health-account-views.md)** – This page shows events that are specific to your account. You can view open, recent, and scheduled changes. You can also view notifications and an event log that shows all events from the past 90 days.
+ **[Your organization events](aws-health-account-views.md#aws-organizations-integration)** – This page shows events that are specific to your organization in AWS Organizations. You can view open, recent, and scheduled changes for your organization. You can also view notifications, as well as an event log that shows all organization events from the past 90 days.
**Note**
If you don't have an AWS account, you can use the [AWS Health Dashboard](aws-health-dashboard-status.md) to learn about general service availability.
If you have an account, we recommend that you sign in to your AWS Health Dashboard to get deeper insights into events and upcoming changes that might affect your services and resources.
**Topics**
+ [Setting up your AWS account](#awshealth-before-you-begin)
+ [Viewing your account events in the AWS Health Dashboard](aws-health-account-views.md)
+ [Configuring Amazon EventBridge](cloud-watch-events-integration.md)
+ [Manage AWS Health notifications in AWS User Notifications](manage-user-notifications.md)
## Setting up your AWS account
Before you can enable AWS Health, you must have an AWS account. If you do not have an AWS account, complete the following steps to create one.
### Sign up for an AWS account
If you do not have an AWS account, complete the following steps to create one.
**To sign up for an AWS account**
1. Open [https://portal.aws.amazon.com/billing/signup](https://portal.aws.amazon.com/billing/signup).
1. Follow the online instructions.
Part of the sign-up procedure involves receiving a phone call or text message and entering a verification code on the phone keypad.
When you sign up for an AWS account, an *AWS account root user* is created. The root user has access to all AWS services and resources in the account. As a security best practice, assign administrative access to a user, and use only the root user to perform [tasks that require root user access](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#root-user-tasks).
AWS sends you a confirmation email after the sign-up process is complete. At any time, you can view your current account activity and manage your account by going to [https://aws.amazon.com/](https://aws.amazon.com/) and choosing **My Account**.
### Create a user with administrative access
After you sign up for an AWS account, secure your AWS account root user, enable AWS IAM Identity Center, and create an administrative user so that you don't use the root user for everyday tasks.
**Secure your AWS account root user**
1. Sign in to the [AWS Management Console](https://console.aws.amazon.com/) as the account owner by choosing **Root user** and entering your AWS account email address. On the next page, enter your password.
For help signing in by using root user, see [Signing in as the root user](https://docs.aws.amazon.com/signin/latest/userguide/console-sign-in-tutorials.html#introduction-to-root-user-sign-in-tutorial) in the *AWS Sign-In User Guide*.
1. Turn on multi-factor authentication (MFA) for your root user.
For instructions, see [Enable a virtual MFA device for your AWS account root user (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/enable-virt-mfa-for-root.html) in the *IAM User Guide*.
**Create a user with administrative access**
1. Enable IAM Identity Center.
For instructions, see [Enabling AWS IAM Identity Center](https://docs.aws.amazon.com//singlesignon/latest/userguide/get-set-up-for-idc.html) in the *AWS IAM Identity Center User Guide*.
1. In IAM Identity Center, grant administrative access to a user.
For a tutorial about using the IAM Identity Center directory as your identity source, see [ Configure user access with the default IAM Identity Center directory](https://docs.aws.amazon.com//singlesignon/latest/userguide/quick-start-default-idc.html) in the *AWS IAM Identity Center User Guide*.
**Sign in as the user with administrative access**
+ To sign in with your IAM Identity Center user, use the sign-in URL that was sent to your email address when you created the IAM Identity Center user.
For help signing in using an IAM Identity Center user, see [Signing in to the AWS access portal](https://docs.aws.amazon.com/signin/latest/userguide/iam-id-center-sign-in-tutorial.html) in the *AWS Sign-In User Guide*.
**Assign access to additional users**
1. In IAM Identity Center, create a permission set that follows the best practice of applying least-privilege permissions.
For instructions, see [ Create a permission set](https://docs.aws.amazon.com//singlesignon/latest/userguide/get-started-create-a-permission-set.html) in the *AWS IAM Identity Center User Guide*.
1. Assign users to a group, and then assign single sign-on access to the group.
For instructions, see [ Add groups](https://docs.aws.amazon.com//singlesignon/latest/userguide/addgroups.html) in the *AWS IAM Identity Center User Guide*.
# Viewing your account events in the AWS Health Dashboard
You can sign in to your account to get personalized events and recommendations.
**To view account events in your AWS Health Dashboard**
1. Open your AWS Health Dashboard at [https://health.aws.amazon.com/health/home](https://health.aws.amazon.com/health/).
1. In the navigation pane, for **Your account health**, you can choose the following options:
1. **[Open and recent issues](#dashboard)** – View recently opened and closed events.
1. **[Scheduled changes](#scheduled-changes-account-events)** – View upcoming events that might affect your services and resources.
1. **[Other notifications](#notification-account-events)** – View all other notifications and ongoing events from the past seven days that might affect your account.
1. **[Event log](#event-log)** – View all events from the past 90 days.
## Open and recent issues
Use the **Open and recent issues** tab to view all ongoing events from the past seven days that might affect your account.
When you choose an event from the dashboard, the **Details** pane appears with information about the event and a list of affected resources. For more information, see [Event details](#event-details).
You can filter the events that appear in any tab by choosing options from the filter list. For example, you can narrow the results by Availability Zone, Region, event end time or last update time, AWS service, and so on.
To see all the events, rather than the recent ones that appear in the dashboard, choose the **[Event log](#event-log)** tab.
**Note**
Currently, you can’t delete notifications for events that appear in your AWS Health Dashboard. After an AWS service resolves an event, the notification is removed from your dashboard view.
**Example : Operational issue event for Amazon Elastic Compute Cloud (Amazon EC2)**
The following image shows an event for launch failures and connectivity issues for Amazon EC2 instances.
![\[Screenshot of your account events in the AWS Health console.\]](http://docs.aws.amazon.com/health/latest/ug/images/health-dashboard-your-account-events.png)
## Scheduled changes
Use the **Scheduled changes** tab to view upcoming events that might affect your account. These events can include scheduled maintenance activities for services and planned lifecycle events that require action to resolve. To help you plan for these activities, a calendar view is provided so that you can map these scheduled changes into a monthly calendar. Filters are available. For more information about planned lifecycle events, see [Planned lifecycle events for AWS Health](aws-health-planned-lifecycle-events.md).
## Other notifications
Use the **Notifications** tab to view all other notifications and ongoing events from the past seven days that might affect your account. This can include events, such as certificate rotations, billing notifications, and security vulnerabilities.
## Event log
Use the **Event log** tab to view all AWS Health events. The log table includes additional columns so that you can filter by **Status** and **Start time**.
When you choose an event in the **Event log** table, the **Details** pane appears with information about the event and the list of affected resources. For more information, see [Event details](#event-details).
You can choose the following filter options to narrow your results:
+ Availability Zone
+ End time
+ Event
+ Event ARN
+ Event category
+ Last update time
+ Region
+ Resource ID / ARN
+ Service
+ Start time
+ Status
**Example : Event log**
The following image shows recent events for the US East (N. Virginia) and US East (Ohio) Regions.
![\[Screenshot of the event log tab in the AWS Health console.\]](http://docs.aws.amazon.com/health/latest/ug/images/event-log-aws-health-console.png)
## Event details
When you choose an event, two tabs appear about the event. The **Details** tab shows the following information:
+ Service
+ Status
+ Region / Availability Zone
+ Whether or not the event is account specific
+ Start and end time
+ Category
+ Number of affected resources
+ Description and a timeline of updates about the event
The **Affected resources** tab shows the following information about any AWS resources that are affected by the event:
+ The resource ID (for example, an Amazon EBS volume ID such as `vol-a1b2c34f`) or Amazon Resource Name (ARN), if available or relevant.
+ For planned lifecycle events, this affected resources list also contains the latest status of the resources (**Pending**, **Unknown**, or **Resolved**). This list usually refreshes once every 24 hours, but might take up to 72 hours to reflect the current status.
You can filter the items that appear in the resources. You can narrow your results by resource ID or ARN.
**Example : AWS Health event for AWS Lambda**
The following screenshot shows an example event for Lambda.
![\[Screenshot of the details pane for an event in the AWS Health console.\]](http://docs.aws.amazon.com/health/latest/ug/images/event-log-details-pane-aws-health-console.png)
## Events types
There are two types of AWS Health events:
+ *Public events* are service events that aren't specific to an account. For example, if there is an issue with Amazon EC2 in an AWS Region, AWS Health provides information about the event, even if you don't use services or resources in that Region.
+ *Account-specific* events are specific to your account or an account in your organization. For example, if there's an issue with an Amazon EC2 instance in an AWS Region that you use, AWS Health provides information about the event and the list of affected Amazon EC2 instances.
You can use the following options to identify if an event is public or account-specific:
+ In the AWS Health Dashboard, choose the **Affected resources** tab for an event. Events with resources are specific to your account. Events without resources are public and are not specific to your account. For more information, see [Getting started with your AWS Health Dashboard](getting-started-health-dashboard.md).
+ Use the AWS Health API to return the `eventScopeCode` parameter. Events can have the `PUBLIC`, `ACCOUNT_SPECIFIC`, or `NONE` value. For more information, see the [DescribeEventDetails](https://docs.aws.amazon.com//health/latest/APIReference/API_DescribeEventDetails.html) operation in the *AWS Health API Reference*.
## Calendar view
**Calendar view** is available in the **scheduled changes** tab to project AWS Health events into a monthly calendar. This view allows you to see scheduled changes up to 3 months into the past and a year into the future.
AWS Health events are displayed by date. Select a date to display a side panel that contains further details on the AWS Health event. **Upcoming** and **ongoing** events are displayed in black. **Completed** events are displayed in grey. If there are more than two events in a date, only the number of black and grey events are shown. Select a date to display a list of AWS Health events in the side panel. You can select an event in the side panel to display information about the event. The side panel has breadcrumbs to navigate to an earlier view.
![\[Scheduled changes calendar view\]](http://docs.aws.amazon.com/health/latest/ug/images/calendar-view2.png)
## Affected resources view
AWS Health events might specify the precise resources that are affected. You can view affected resources in the **Affected Resources** tab of the AWS Health event. To view the status, select the AWS Health event. The status displays in the affected resources tab in the side panel. For planned lifecycle events, AWS Health events provide daily updates of the affected resources' status.
Account-level AWS Health events display a summary of affected resources statuses at the top of the **Affected Resources** tab. A list of affected resources is displayed in a table along with the corresponding status. Planned lifecycle events are an example of event types that use the resource status field. To learn more about planned lifecycle events, see [Planned lifecycle events for AWS Health](aws-health-planned-lifecycle-events.md).
When you access the organization view, AWS Health events display a summary of the status of all affected resources for all included accounts. After the summary is a list of affected accounts and the number of pending resources for that account. Select the account number or the number of pending resources to display the account view summary. The account view summary has breadcrumbs to navigate back to the organizational list of affected accounts. A summary of affected resource statuses is displayed at the top of the split panel.
You can download the list of affected resources in the affected resources tab in CSV or JSON format. In organizational view, the downloaded file includes all resources in the accounts listed. Navigate to the account level in organizational view to include only resources for that account in the downloaded file. Each affected resource in the downloaded file includes the AWS account ID, the eventARN, the entity name, the entityARN, status, and the last updated time of the resource. If filters are activated, the downloaded file only includes the filtered results.
You can download only one file at a time. The files are automatically downloaded into the default download folder of your browser and have a preset file name based on the AWS Region, the event title, the event start date, and the download date.
![\[Affected resources view\]](http://docs.aws.amazon.com/health/latest/ug/images/affected-resources.png)
## Time zone settings
You can view the events in the AWS Health Dashboard in your local time zone or in UTC. If you change the time zone in your AWS Health Dashboard, all timestamps in the dashboard and public events update to the time zone that you specify.
**To update your time zone settings**
1. Open your AWS Health Dashboard at [https://health.aws.amazon.com/health/home](https://health.aws.amazon.com/health/).
1. At the bottom of the page, choose **Cookie preferences**.
1. Select **Allowed** for Functional cookies. Then choose **Save preferences**.
1. In the navigation pane of your AWS Health Dashboard, choose **Time zone settings**.
1. Select a time zone for your AWS Health Dashboard sessions. Then choose **Save changes**.
## Your organization health
AWS Health integrates with AWS Organizations so that you can view events for all accounts that are part of your organization. This provides you a centralized view for events that appear in your organization. You can use these events to monitor for changes in your resources, services, and applications.
For more information, see [Aggregating AWS Health events across accounts](aggregate-events.md).
![\[Screenshot of the Enable organizational view page in the AWS Health console.\]](http://docs.aws.amazon.com/health/latest/ug/images/organizational-view-aws-health-console.png)
## Alerts for AWS Health events
Your AWS Health Dashboard has a bell icon in the console navigation bar with an alert menu. This feature displays the number of recent AWS Health events that appear on the dashboard in each category. This bell icon appears on several AWS consoles, such as those for Amazon EC2, Amazon Relational Database Service (Amazon RDS), AWS Identity and Access Management (IAM), and AWS Trusted Advisor.
Choose the bell icon to see if recent events affect your account. You can then choose an event to navigate to your AWS Health Dashboard for more information.
**Example : Open events**
The following image shows open and notification events for an account.
![\[Screenshot of the notification bell icon in the AWS Health console.\]](http://docs.aws.amazon.com/health/latest/ug/images/aws-health-dashboard-bell-icon.png)
# Configuring Amazon EventBridge
Use EventBridge to detect and react to changes for AWS Health events. You can monitor specific AWS Health events that occur in your account, and then set up rules so that AWS Health notifies you, or you take action, when events change.
**Use EventBridge with AWS Health**
1. Open your AWS Health Dashboard at [https://health.aws.amazon.com/health/home](https://health.aws.amazon.com/health/).
1. To navigate to the EventBridge console to create a rule, do one of the following:
+ From the navigation pane, under **Health Integrations**, choose **Amazon EventBridge**.
+ Under **Configure EventBridge**, choose **Go to EventBridge**.
1. Follow this procedure to create rules and monitor for events. See [Monitoring events in AWS Health with Amazon EventBridge](cloudwatch-events-health.md).
# Manage AWS Health notifications in AWS User Notifications
AWS managed notifications in AWS User Notifications lets you receive and manage notifications about events that affect your AWS accounts and services. When you use AWS managed notifications in AWS User Notifications, you can specify which AWS Health event categories to receive, set up organizational view for emails, and get consolidated notifications instead of multiple similar emails.
You can choose the following additional channels to receive your AWS Health events through AWS User Notifications:
+ Email
+ Chat
+ Push notifications to the AWS Console Mobile Application
While these notifications aren’t as detailed as direct AWS Health tools, they provide an effective way to notify stakeholders of issues and changes.
**Note**
For comprehensive visibility into AWS Health event details, including affected resource IDs, current status (open or closed), and resource status, it's a best practice to use one of the following AWS Health tools:
The AWS Health API
The aws.health source in Amazon EventBridge
The Health Dashboard
These tools provide the most detailed and real-time information about ongoing events and changes that might affect your workloads.
## Configure your AWS managed notifications subscription for AWS Health events
To configure your AWS managed notifications subscription, complete the following steps:
1. Open User Notifications in the [AWS Management Console](https://console.aws.amazon.com/notifications).
1. In the navigation pane, choose **AWS managed notifications subscriptions**.
1. You can manage your AWS Health event notifications by category. For more information, see [Adding and removing account contacts for AWS managed notifications in AWS User Notifications](https://docs.aws.amazon.com/notifications/latest/userguide/manage-mns.html#Add-remove-account-contacts).
**Note**
AWS Health migrated email delivery to AWS managed notifications in AWS User Notifications. Since December 15, 2025, you receive emails from AWS managed notifications. For more information, see *What changed in the migration to AWS managed notifications?* in the [AWS managed notifications in AWS User Notifications FAQ](#manage-user-notifications-faq).
## AWS managed notifications in AWS User Notifications FAQ
### What changed in the migration to AWS managed notifications?
By default, emails regarding managed notifications are sent to your existing account contacts (root, operations, billing, and security email addresses). The emails that you receive from AWS managed notifications come from `health@aws.com` instead of `no-reply-aws@amazon.com`, and the format of the email changes. If you previously set up email rules for AWS Health notifications, such as routing an email by sender ID or scraping the content of the email, then you must update this setup to match the new email format. If you require automation through push notifications, then we recommend that you evaluate AWS Health events sent through Amazon EventBridge as an alternative to managed notifications.
### How does aggregation work for emails and how do I enable this feature?
AWS managed notification aggregates AWS Health events that impact multiple accounts within the same AWS Organizations organization into a single aggregated notification. You can view the aggregated organization in the management account's notifications center. Managed notifications emails the aggregated notification to the management account's contacts. To reduce duplicate emails, AWS managed notifications sends one notification when account contacts are shared between management and member accounts.
To enable aggregation, you must have AWS Organizations configured and grant trusted access between your management account and the AWS User Notifications service.
For more information, see [AWS managed notifications aggregation in AWS User Notifications](https://docs.aws.amazon.com/notifications/latest/userguide/managed-notification-aggregation.html).
### Do I have to enable AWS Organizations trusted access with AWS User Notifications to receive aggregated email from AWS managed notifications?
Yes, trusted access with AWS User Notifications from AWS Organizations is required.
### What's the difference between enabling trusted access through AWS Organizations with AWS Health and with AWS User Notifications?
Organizational trust and the associated delegated administrator privileges are assigned by service and act as guardrails against overextended permissions. Trusted access for AWS Health enables organizational view for the Health Dashboard, the AWS Health APIs, AWS Health events sent through Amazon EventBridge, and notification configurations in User Notifications. Trusted access for AWS User Notifications enables aggregate notifications within AWS managed notifications. Because trusted access isn't shared, setting up delegated administrators needs to be added separately for each service.
### Is there a way to keep plain text emails for my specific use case?
No. The current plain text AWS Health emails are disabled after the migration completes. If you use email rules to drive different workflows, we recommend that you evaluate AWS Health events sent through Amazon EventBridge as an alternative.
### What do AWS managed notifications categories correspond to in the AWS Health schema?
Health operations, Security, and Billing notifications correspond to AWS Health account notifications and scheduled changes that have the operations, security, and billing persona respectively. AWS Health events with more than one persona tag are sent through the Security and Billing categories. Account-specific issues include issue category health events that are specific to an AWS account.
Public service events aren't available through AWS managed notifications.