# Amazon Health and Amazon Organizations
<a name="services-that-can-integrate-health"></a>

Amazon Health provides ongoing visibility into your resource performance and the availability of your Amazon Web Services services and accounts. Amazon Health delivers events when your Amazon resources and services are impacted by an issue or will be affected by upcoming changes. After you enable organizational view, a user in the organization’s management account can aggregate Amazon Health events across all accounts in the organization. Organizational view only shows Amazon Health events delivered after the feature is enabled and retains them for 90 days. 

You can enable organizational view by using the Amazon Health console, the Amazon Command Line Interface (Amazon CLI), or the Amazon Health API. 

For more information, see [Aggregating Amazon Health events](https://docs.amazonaws.cn/health/latest/ug/aggregate-events.html) in the *Amazon Health User Guide*.

Use the following information to help you integrate Amazon Health with Amazon Organizations.



## Service-linked roles for integration
<a name="integrate-enable-slr-health"></a>

The `AWSServiceRoleForHealth_Organizations` service-linked role allows Amazon Health to perform supported operations within your organization's accounts in your organization.

This role is created automatically in your organization's management account when you enable trusted access by calling the [EnableHealthServiceAccessForOrganization](https://docs.amazonaws.cn/health/latest/APIReference/API_EnableHealthServiceAccessForOrganization.html) API operation. Otherwise, create the role using the Amazon Health console, API, or CLI, as described in [Creating a service-linked role](https://docs.amazonaws.cn/IAM/latest/UserGuide/using-service-linked-roles.html#create-service-linked-role) in the [IAM User Guide](https://docs.amazonaws.cn/IAM/latest/UserGuide/).

You can delete or modify this role only if you disable trusted access between Amazon Health and Organizations, or if you remove the member account from the organization.

## Service principals used by the service-linked roles
<a name="integrate-enable-svcprin-health"></a>

The service-linked role in the previous section can be assumed only by the service principals authorized by the trust relationships defined for the role. The service-linked roles used by Amazon Health grant access to the following service principals:
+ `health.amazonaws.com`

## Enabling trusted access with Amazon Health
<a name="integrate-enable-ta-health"></a>

For information about the permissions needed to enable trusted access, see [Permissions required to enable trusted access](orgs_integrate_services.md#orgs_trusted_access_perms).

When you the enable organizational view feature for Amazon Health, trusted access is also enabled for you automatically.

You can enable trusted access using either the Amazon Health console or the Amazon Organizations console.

**Important**  
We strongly recommend that whenever possible, you use the Amazon Health console or tools to enable integration with Organizations. This lets Amazon Health perform any configuration that it requires, such as creating resources needed by the service. Proceed with these steps only if you can’t enable integration using the tools provided by Amazon Health. For more information, see [this note](orgs_integrate_services.md#important-note-about-integration).   
If you enable trusted access by using the Amazon Health console or tools then you don’t need to complete these steps.

**To enable trusted access using the Amazon Health console**  
You can enable trusted access by using Amazon Health and one of the following options:
+ Use the Amazon Health console. For more information, see [Organizational view (console) ](https://docs.amazonaws.cn/health/latest/ug/enable-organizational-view-in-health-console.html) in the *Amazon Health User Guide*. 
+ Use the Amazon CLI. For more information, see [Organizational view (CLI) ](https://docs.amazonaws.cn/health/latest/ug/enable-organizational-view-from-aws-command-line.html) in the *Amazon Health User Guide*. 
+ Call the [EnableHealthServiceAccessForOrganization](https://docs.amazonaws.cn/health/latest/APIReference/API_EnableHealthServiceAccessForOrganization.html) API operation.

You can enable trusted access by running a Organizations Amazon CLI command, or by calling an Organizations API operation in one of the Amazon SDKs.

------
#### [ Amazon CLI, Amazon API ]

**To enable trusted service access using the Organizations CLI/SDK**  
Use the following Amazon CLI commands or API operations to enable trusted service access:
+ Amazon CLI: [enable-aws-service-access](https://docs.amazonaws.cn/cli/latest/reference/organizations/enable-aws-service-access.html)

  Run the following command to enable Amazon Health as a trusted service with Organizations.

  ```
  $ aws organizations enable-aws-service-access \
      --service-principal health.amazonaws.com
  ```

  This command produces no output when successful.
+ Amazon API: [EnableAWSServiceAccess](https://docs.amazonaws.cn/organizations/latest/APIReference/API_EnableAWSServiceAccess.html)

------

## Disabling trusted access with Amazon Health
<a name="integrate-disable-ta-health"></a>

For information about the permissions needed to disable trusted access, see [Permissions required to disable trusted access](orgs_integrate_services.md#orgs_trusted_access_disable_perms).

After you disable the organizational view feature, Amazon Health stops aggregating events for all other accounts in your organization. This also disables trusted access for you automatically. 

You can disable trusted access using either the Amazon Health or the Amazon Organizations tools.

**Important**  
We strongly recommend that whenever possible, you use the Amazon Health console or tools to disable integration with Organizations. This lets Amazon Health perform any clean up that it requires, such as deleting resources or access roles that are no longer needed by the service. Proceed with these steps only if you can’t disable integration using the tools provided by Amazon Health.  
If you disable trusted access by using the Amazon Health console or tools then you don’t need to complete these steps.

**To disable trusted access using the Amazon Health console**  
You can disable trusted access with one of the following options:
+ Use the Amazon Health console. For more information, see [Disabling organizational view (console) ](https://docs.amazonaws.cn/health/latest/ug/enable-organizational-view-in-health-console.html#disabling-organizational-view-console) in the *Amazon Health User Guide*.
+ Use the Amazon CLI. For more information, see [Disabling organizational view (CLI) ](https://docs.amazonaws.cn//health/latest/ug/enable-organizational-view-from-aws-command-line.html#disabling-organizational-view) in the *Amazon Health User Guide*. 
+ Call the [DisableHealthServiceAccessForOrganization](https://docs.amazonaws.cn/health/latest/APIReference/API_DisableHealthServiceAccessForOrganization.html) API operation.

You can disable trusted access by running a Organizations Amazon CLI command, or by calling an Organizations API operation in one of the Amazon SDKs.

------
#### [ Amazon CLI, Amazon API ]

**To disable trusted service access using the Organizations CLI/SDK**  
Use the following Amazon CLI commands or API operations to disable trusted service access:
+ Amazon CLI: [disable-aws-service-access](https://docs.amazonaws.cn/cli/latest/reference/organizations/disable-aws-service-access.html)

  Run the following command to disable Amazon Health as a trusted service with Organizations.

  ```
  $ aws organizations disable-aws-service-access \
      --service-principal health.amazonaws.com
  ```

  This command produces no output when successful.
+ Amazon API: [DisableAWSServiceAccess](https://docs.amazonaws.cn/organizations/latest/APIReference/API_DisableAWSServiceAccess.html)

------

## Enabling a delegated administrator account for Amazon Health
<a name="integrate-enable-da-health"></a>

When you designate a member account as a delegated administrator for the organization, users and roles from that account can perform administrative actions for Amazon Health that otherwise can be performed only by users or roles in the organization's management account. This helps you to separate management of the organization from management of Amazon Health.

**To designate a member account as a delegated administrator for Amazon Health**  
See [Register a delegated administrator for your organizational view](https://docs.amazonaws.cn/health/latest/ug/delegated-administrator-organizational-view.html#register-a-delegated-administrator)

**To remove a delegated administrator for Amazon Health**  
See [Remove a delegated administrator from your organizational view](https://docs.amazonaws.cn/health/latest/ug/delegated-administrator-organizational-view.html#remove-a-delegated-administrator)