# Identity and access management for Amazon Health
Identity and access management

Amazon Identity and Access Management (IAM) is an Amazon Web Services service that helps an administrator securely control access to Amazon resources. IAM administrators control who can be *authenticated* (signed in) and *authorized* (have permissions) to use Amazon Health resources. IAM is an Amazon Web Services service that you can use with no additional charge.

**Topics**
+ [

## Audience
](#security_iam_audience)
+ [

## Authenticating with identities
](#security_iam_authentication)
+ [

## Managing access using policies
](#security_iam_access-manage)
+ [

# How Amazon Health works with IAM
](security_iam_service-with-iam.md)
+ [

# Amazon Health identity-based policy examples
](security_iam_id-based-policy-examples.md)
+ [

# Troubleshooting Amazon Health identity and access
](security_iam_troubleshoot.md)
+ [

# Using service-linked roles for Amazon Health
](using-service-linked-roles.md)
+ [

# Amazon managed policies for Amazon Health
](security-iam-awsmanpol.md)

## Audience


How you use Amazon Identity and Access Management (IAM) differs based on your role:
+ **Service user** - request permissions from your administrator if you cannot access features (see [Troubleshooting Amazon Health identity and access](security_iam_troubleshoot.md))
+ **Service administrator** - determine user access and submit permission requests (see [How Amazon Health works with IAM](security_iam_service-with-iam.md))
+ **IAM administrator** - write policies to manage access (see [Amazon Health identity-based policy examples](security_iam_id-based-policy-examples.md))

## Authenticating with identities


Authentication is how you sign in to Amazon using your identity credentials. You must be authenticated as the Amazon Web Services account root user, an IAM user, or by assuming an IAM role.

For programmatic access, Amazon provides an SDK and CLI to cryptographically sign requests. For more information, see [Amazon Signature Version 4 for API requests](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_sigv.html) in the *IAM User Guide*.

### Amazon account root user


 When you create an Amazon Web Services account, you begin with one sign-in identity called the Amazon Web Services account *root user* that has complete access to all Amazon Web Services services and resources. We strongly recommend that you don't use the root user for everyday tasks. For tasks that require root user credentials, see [Tasks that require root user credentials](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_root-user.html#root-user-tasks) in the *IAM User Guide*. 

### IAM users and groups


An *[IAM user](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_users.html)* is an identity with specific permissions for a single person or application. We recommend using temporary credentials instead of IAM users with long-term credentials. For more information, see [Require human users to use federation with an identity provider to access Amazon using temporary credentials](https://docs.amazonaws.cn/IAM/latest/UserGuide/best-practices.html#bp-users-federation-idp) in the *IAM User Guide*.

An [https://docs.amazonaws.cn/IAM/latest/UserGuide/id_groups.html](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_groups.html) specifies a collection of IAM users and makes permissions easier to manage for large sets of users. For more information, see [Use cases for IAM users](https://docs.amazonaws.cn/IAM/latest/UserGuide/gs-identities-iam-users.html) in the *IAM User Guide*.

### IAM roles


An *[IAM role](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_roles.html)* is an identity with specific permissions that provides temporary credentials. You can assume a role by [switching from a user to an IAM role (console)](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_roles_use_switch-role-console.html) or by calling an Amazon CLI or Amazon API operation. For more information, see [Methods to assume a role](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_roles_manage-assume.html) in the *IAM User Guide*.

IAM roles are useful for federated user access, temporary IAM user permissions, cross-account access, cross-service access, and applications running on Amazon EC2. For more information, see [Cross account resource access in IAM](https://docs.amazonaws.cn/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.

## Managing access using policies


You control access in Amazon by creating policies and attaching them to Amazon identities or resources. A policy defines permissions when associated with an identity or resource. Amazon evaluates these policies when a principal makes a request. Most policies are stored in Amazon as JSON documents. For more information about JSON policy documents, see [Overview of JSON policies](https://docs.amazonaws.cn/IAM/latest/UserGuide/access_policies.html#access_policies-json) in the *IAM User Guide*.

Using policies, administrators specify who has access to what by defining which **principal** can perform **actions** on what **resources**, and under what **conditions**.

By default, users and roles have no permissions. An IAM administrator creates IAM policies and adds them to roles, which users can then assume. IAM policies define permissions regardless of the method used to perform the operation.

### Identity-based policies


Identity-based policies are JSON permissions policy documents that you attach to an identity (user, group, or role). These policies control what actions identities can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.amazonaws.cn/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*.

Identity-based policies can be *inline policies* (embedded directly into a single identity) or *managed policies* (standalone policies attached to multiple identities). To learn how to choose between managed and inline policies, see [Choose between managed policies and inline policies](https://docs.amazonaws.cn/IAM/latest/UserGuide/access_policies-choosing-managed-or-inline.html) in the *IAM User Guide*.

### Resource-based policies


Resource-based policies are JSON policy documents that you attach to a resource. Examples include IAM *role trust policies* and Amazon S3 *bucket policies*. In services that support resource-based policies, service administrators can use them to control access to a specific resource. You must [specify a principal](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy.

Resource-based policies are inline policies that are located in that service. You can't use Amazon managed policies from IAM in a resource-based policy.

Amazon Health supports resource-based conditions. You can specify which Amazon Health events that users can view. For example, you might create a policy that only allows an IAM user access to specific Amazon EC2 events in the Amazon Health Dashboard. 

For more information, see [Resources](security_iam_service-with-iam.md#security_iam_service-with-iam-id-based-policies-resources).

### Access control lists


Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy document format.

Amazon S3, Amazon WAF, and Amazon VPC are examples of services that support ACLs. To learn more about ACLs, see [Access control list (ACL) overview](https://docs.amazonaws.cn/AmazonS3/latest/userguide/acl-overview.html) in the *Amazon Simple Storage Service Developer Guide*.

Amazon Health doesn't support ACLs.

### Other policy types


Amazon supports additional policy types that can set the maximum permissions granted by more common policy types:
+ **Permissions boundaries** – Set the maximum permissions that an identity-based policy can grant to an IAM entity. For more information, see [Permissions boundaries for IAM entities](https://docs.amazonaws.cn/IAM/latest/UserGuide/access_policies_boundaries.html) in the *IAM User Guide*.
+ **Service control policies (SCPs)** – Specify the maximum permissions for an organization or organizational unit in Amazon Organizations. For more information, see [Service control policies](https://docs.amazonaws.cn/organizations/latest/userguide/orgs_manage_policies_scps.html) in the *Amazon Organizations User Guide*.
+ **Resource control policies (RCPs)** – Set the maximum available permissions for resources in your accounts. For more information, see [Resource control policies (RCPs)](https://docs.amazonaws.cn/organizations/latest/userguide/orgs_manage_policies_rcps.html) in the *Amazon Organizations User Guide*.
+ **Session policies** – Advanced policies passed as a parameter when creating a temporary session for a role or federated user. For more information, see [Session policies](https://docs.amazonaws.cn/IAM/latest/UserGuide/access_policies.html#policies_session) in the *IAM User Guide*.

### Multiple policy types


When multiple types of policies apply to a request, the resulting permissions are more complicated to understand. To learn how Amazon determines whether to allow a request when multiple policy types are involved, see [Policy evaluation logic](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_policies_evaluation-logic.html) in the *IAM User Guide*.

# How Amazon Health works with IAM


Before you use IAM to manage access to Amazon Health, you should understand what IAM features are available to use with Amazon Health. To get a high-level view of how Amazon Health and other Amazon services work with IAM, see [Amazon Services That Work with IAM](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*.

**Topics**
+ [

## Amazon Health identity-based policies
](#security_iam_service-with-iam-id-based-policies)
+ [

## Amazon Health resource-based policies
](#security_iam_service-with-iam-resource-based-policies)
+ [

## Authorization based on Amazon Health tags
](#security_iam_service-with-iam-tags)
+ [

## Amazon Health IAM roles
](#security_iam_service-with-iam-roles)

## Amazon Health identity-based policies


With IAM identity-based policies, you can specify allowed or denied actions and resources as well as the conditions under which actions are allowed or denied. Amazon Health supports specific actions, resources, and condition keys. To learn about all of the elements that you use in a JSON policy, see [IAM JSON Policy Elements Reference](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_policies_elements.html) in the *IAM User Guide*.

### Actions


Administrators can use Amazon JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**.

The `Action` element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Include actions in a policy to grant permissions to perform the associated operation.

Policy actions in Amazon Health use the following prefix before the action: `health:`. For example, to grant someone permission to view detailed information about specified events with the [DescribeEventDetails](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeEventDetails.html) API operation, you include the `heath:DescribeEventDetails` action in the policy. 

Policy statements must include an `Action` or `NotAction` element. Amazon Health defines its own set of actions that describe tasks that you can perform with this service.

To specify multiple actions in a single statement, separate them with commas as follows.

```
"Action": [
      "health:action1",
      "health:action2"
```

You can specify multiple actions using wildcards (\$1). For example, to specify all actions that begin with the word `Describe`, include the following action.

```
"Action": "health:Describe*"
```



To see a list of Amazon Health actions, see [Actions Defined by Amazon Health](https://docs.amazonaws.cn/IAM/latest/UserGuide/list_awshealthapisandnotifications.html#awshealthapisandnotifications-actions-as-permissions) in the *IAM User Guide*.

### Resources


Administrators can use Amazon JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**.

The `Resource` JSON policy element specifies the object or objects to which the action applies. As a best practice, specify a resource using its [Amazon Resource Name (ARN)](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference-arns.html). For actions that don't support resource-level permissions, use a wildcard (\$1) to indicate that the statement applies to all resources.

```
"Resource": "*"
```



An Amazon Health event has the following Amazon Resource Name (ARN) format.

```
arn:${Partition}:health:*::event/service/event-type-code/event-ID
```

For example, to specify the `EC2_INSTANCE_RETIREMENT_SCHEDULED_ABC123-DEF456` event in your statement, use the following ARN.

```
"Resource": "arn:aws:health:*::event/EC2/EC2_INSTANCE_RETIREMENT_SCHEDULED/EC2_INSTANCE_RETIREMENT_SCHEDULED_ABC123-DEF456"
```

To specify all Amazon Health events for Amazon EC2 that belong to a specific account, use the wildcard (\$1).

```
"Resource": "arn:aws:health:*::event/EC2/*/*"
```

For more information about the format of ARNs, see [Amazon Resource Names (ARNs) and Amazon Service Namespaces](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html).

Some Amazon Health actions can't be performed on a specific resource. In those cases, you must use the wildcard (\$1).

```
"Resource": "*"
```

Amazon Health API operations can involve multiple resources. For example, the [DescribeEvents](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeEvents.html) operation returns information about events that meet a specified filter criteria. This means that an IAM user must have permissions to view this event. 

To specify multiple resources in a single statement, separate the ARNs with commas. 

```
"Resource": [
      "resource1",
      "resource2"
```

Amazon Health supports only resource-level permissions for health events and only for the [DescribeAffectedEntities](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeAffectedEntities.html) and [DescribeEventDetails](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeEventDetails.html) API operations. For more information, see [Resource- and action-based conditions](security_iam_id-based-policy-examples.md#resource-action-based-conditions).

To see a list of Amazon Health resource types and their ARNs, see [Resources Defined by Amazon Health](https://docs.amazonaws.cn/IAM/latest/UserGuide/list_awshealthapisandnotifications.html#awshealthapisandnotifications-resources-for-iam-policies) in the *IAM User Guide*. To learn with which actions you can specify the ARN of each resource, see [Actions Defined by Amazon Health](https://docs.amazonaws.cn/IAM/latest/UserGuide/list_awshealthapisandnotifications.html#awshealthapisandnotifications-actions-as-permissions).

### Condition keys


Administrators can use Amazon JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**.

The `Condition` element specifies when statements execute based on defined criteria. You can create conditional expressions that use [condition operators](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html), such as equals or less than, to match the condition in the policy with values in the request. To see all Amazon global condition keys, see [Amazon global condition context keys](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*.

Amazon Health defines its own set of condition keys and also supports using some global condition keys. To see all Amazon global condition keys, see [Amazon Global Condition Context Keys](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*.



The [DescribeAffectedEntities](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeAffectedEntities.html) and [DescribeEventDetails](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeEventDetails.html) API operations support the `health:eventTypeCode` and `health:service` condition keys.

To see a list of Amazon Health condition keys, see [Condition Keys for Amazon Health](https://docs.amazonaws.cn/IAM/latest/UserGuide/list_awshealthapisandnotifications.html#awshealthapisandnotifications-policy-keys) in the *IAM User Guide*. To learn with which actions and resources you can use a condition key, see [Actions Defined by Amazon Health](https://docs.amazonaws.cn/IAM/latest/UserGuide/list_awshealthapisandnotifications.html#awshealthapisandnotifications-actions-as-permissions).

### Examples




To view examples of Amazon Health identity-based policies, see [Amazon Health identity-based policy examples](security_iam_id-based-policy-examples.md).

## Amazon Health resource-based policies


Resource-based policies are JSON policy documents that specify what actions a specified principal can perform on the Amazon Health resource and under what conditions. Amazon Health supports resource-based permissions policies for health events. Resource-based policies let you grant usage permission to other accounts on a per-resource basis. You can also use a resource-based policy to allow an Amazon service to access your Amazon Health events.

To enable cross-account access, you can specify an entire account or IAM entities in another account as the [principal in a resource-based policy](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_policies_elements_principal.html). Adding a cross-account principal to a resource-based policy is only half of establishing the trust relationship. When the principal and the resource are in different Amazon accounts, you must also grant the principal entity permission to access the resource. Grant permission by attaching an identity-based policy to the entity. However, if a resource-based policy grants access to a principal in the same account, no additional identity-based policy is required. For more information, see [How IAM Roles Differ from Resource-based Policies ](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_roles_compare-resource-policies.html)in the *IAM User Guide*.

Amazon Health supports only resource-based policies for the [DescribeAffectedEntities](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeAffectedEntities.html) and [DescribeEventDetails](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeEventDetails.html) API operations. You can specify these actions in a policy to define which principal entities (accounts, users, roles, and federated users) can perform actions on the Amazon Health event.

### Examples




To view examples of Amazon Health resource-based policies, see [Resource- and action-based conditions](security_iam_id-based-policy-examples.md#resource-action-based-conditions).

## Authorization based on Amazon Health tags


Amazon Health doesn't support tagging resources or controlling access based on tags.

## Amazon Health IAM roles


An [IAM role](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_roles.html) is an entity within your Amazon account that has specific permissions.

### Using temporary credentials with Amazon Health


You can use temporary credentials to sign in with federation, assume an IAM role, or to assume a cross-account role. You obtain temporary security credentials by calling Amazon STS API operations such as [AssumeRole](https://docs.amazonaws.cn/STS/latest/APIReference/API_AssumeRole.html) or [GetFederationToken](https://docs.amazonaws.cn/STS/latest/APIReference/API_GetFederationToken.html). 

Amazon Health supports using temporary credentials. 

### Service-linked roles


[Service-linked roles](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role) allow Amazon services to access resources in other services to complete an action on your behalf. Service-linked roles appear in your IAM account and are owned by the service. An IAM administrator can view but not edit the permissions for service-linked roles.

Amazon Health supports service-linked roles to integrate with Amazon Organizations. The service-linked role is named `AWSServiceRoleForHealth_Organizations`. Attached to the role is the [Health\$1OrganizationsServiceRolePolicy](https://console.amazonaws.cn//iam/home?#/policies/arn:aws:iam::aws:policy/aws-service-role/Health_OrganizationsServiceRolePolicy) Amazon managed policy. The Amazon managed policy allows Amazon Health to access health events from other Amazon accounts in the organization.

You can use the [EnableHealthServiceAccessForOrganization](https://docs.amazonaws.cn//health/latest/APIReference/API_EnableHealthServiceAccessForOrganization.html) operation to create the service-linked role in the account. However, if you want to disable this feature, you must first call the [DisableHealthServiceAccessForOrganization](https://docs.amazonaws.cn//health/latest/APIReference/API_DisableHealthServiceAccessForOrganization.html) operation. You can then delete the role through the IAM console, IAM API, or Amazon Command Line Interface (Amazon CLI). For more information, see [Using service-linked roles](https://docs.amazonaws.cn/IAM/latest/UserGuide/using-service-linked-roles.html) in the *IAM User Guide*.

For more information, see [Aggregating Amazon Health events across accounts](aggregate-events.md).

### Service roles


This feature allows a service to assume a [service role](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-role) on your behalf. This role allows the service to access resources in other services to complete an action on your behalf. Service roles appear in your IAM account and are owned by the account. This means that an IAM administrator can change the permissions for this role. However, doing so might break the functionality of the service.

Amazon Health doesn't support service roles. 

# Amazon Health identity-based policy examples
Identity-based policy examples

By default, IAM users and roles don't have permission to create or modify Amazon Health resources. They also can't perform tasks using the Amazon Web Services Management Console, Amazon CLI, or Amazon API. An IAM administrator must create IAM policies that grant users and roles permission to perform specific API operations on the specified resources they need. The administrator must then attach those policies to the IAM users or groups that require those permissions.

To learn how to create an IAM identity-based policy using these example JSON policy documents, see [Creating Policies on the JSON Tab](https://docs.amazonaws.cn/IAM/latest/UserGuide/access_policies_create.html#access_policies_create-json-editor) in the *IAM User Guide*.

**Topics**
+ [

## Policy best practices
](#security_iam_service-with-iam-policy-best-practices)
+ [

## Using the Amazon Health console
](#security_iam_id-based-policy-examples-console)
+ [

## Allow users to view their own permissions
](#security_iam_id-based-policy-examples-view-own-permissions)
+ [

## Accessing the Amazon Health Dashboard and the Amazon Health API
](#security_iam_id-based-policy-examples-access-dashboard)
+ [

## Resource- and action-based conditions
](#resource-action-based-conditions)

## Policy best practices


Identity-based policies determine whether someone can create, access, or delete Amazon Health resources in your account. These actions can incur costs for your Amazon Web Services account. When you create or edit identity-based policies, follow these guidelines and recommendations:
+ **Get started with Amazon managed policies and move toward least-privilege permissions** – To get started granting permissions to your users and workloads, use the *Amazon managed policies* that grant permissions for many common use cases. They are available in your Amazon Web Services account. We recommend that you reduce permissions further by defining Amazon customer managed policies that are specific to your use cases. For more information, see [Amazon managed policies](https://docs.amazonaws.cn/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) or [Amazon managed policies for job functions](https://docs.amazonaws.cn/IAM/latest/UserGuide/access_policies_job-functions.html) in the *IAM User Guide*.
+ **Apply least-privilege permissions** – When you set permissions with IAM policies, grant only the permissions required to perform a task. You do this by defining the actions that can be taken on specific resources under specific conditions, also known as *least-privilege permissions*. For more information about using IAM to apply permissions, see [ Policies and permissions in IAM](https://docs.amazonaws.cn/IAM/latest/UserGuide/access_policies.html) in the *IAM User Guide*.
+ **Use conditions in IAM policies to further restrict access** – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific Amazon Web Services service, such as Amazon CloudFormation. For more information, see [ IAM JSON policy elements: Condition](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the *IAM User Guide*.
+ **Use IAM Access Analyzer to validate your IAM policies to ensure secure and functional permissions** – IAM Access Analyzer validates new and existing policies so that the policies adhere to the IAM policy language (JSON) and IAM best practices. IAM Access Analyzer provides more than 100 policy checks and actionable recommendations to help you author secure and functional policies. For more information, see [Validate policies with IAM Access Analyzer](https://docs.amazonaws.cn/IAM/latest/UserGuide/access-analyzer-policy-validation.html) in the *IAM User Guide*.
+ **Require multi-factor authentication (MFA)** – If you have a scenario that requires IAM users or a root user in your Amazon Web Services account, turn on MFA for additional security. To require MFA when API operations are called, add MFA conditions to your policies. For more information, see [ Secure API access with MFA](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_credentials_mfa_configure-api-require.html) in the *IAM User Guide*.

For more information about best practices in IAM, see [Security best practices in IAM](https://docs.amazonaws.cn/IAM/latest/UserGuide/best-practices.html) in the *IAM User Guide*.

## Using the Amazon Health console
Using the console

To access the Amazon Health console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the Amazon Health resources in your Amazon account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (IAM users or roles) with that policy.

To ensure that those entities can still use the Amazon Health console, you can attach the following Amazon managed policy, [https://console.amazonaws.cn//iam/home?#/policies/arn:aws:iam::aws:policy/AWSHealthFullAccess](https://console.amazonaws.cn//iam/home?#/policies/arn:aws:iam::aws:policy/AWSHealthFullAccess).

The `AWSHealthFullAccess` policy grants an entity full access to the following: 
+ Enable or disable the Amazon Health organizational view feature for all accounts in an Amazon organization
+ The Amazon Health Dashboard in the Amazon Health console
+ Amazon Health API operations and notifications
+ View information about accounts that are part of your Amazon organization
+ View the organizational units (OU) of the management account

**Example : AWSHealthFullAccess**    
****  

```
{
    "Version":"2012-10-17",		 	 	 
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "organizations:EnableAWSServiceAccess",
                "organizations:DisableAWSServiceAccess"         
            ],
            "Resource": "*",
            "Condition": {
                "StringEquals": {
                    "organizations:ServicePrincipal": "health.amazonaws.com"
                }
            }
        },
        {
            "Effect": "Allow",
            "Action": [
                "health:*",
                "organizations:DescribeAccount",    
                "organizations:ListAccounts",
                "organizations:ListDelegatedAdministrators",
                "organizations:ListParents"
            ],
            "Resource": "*"
        },
        {
            "Effect": "Allow",
            "Action": "iam:CreateServiceLinkedRole",
            "Resource": "*",
            "Condition": {
                "StringEquals": {
                    "iam:AWSServiceName": "health.amazonaws.com"
                }
            }
        }
    ]
}
```

**Note**  
You can also use the `Health_OrganizationsServiceRolePolicy` Amazon managed policy, so that Amazon Health can view events for other accounts in your organization. For more information, see [Using service-linked roles for Amazon Health](using-service-linked-roles.md).

You don't need to allow minimum console permissions for users that are making calls only to the Amazon CLI or the Amazon API. Instead, allow access to only the actions that match the API operation that you're trying to perform.

For more information, see [Adding Permissions to a User](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) in the *IAM User Guide*.

## Allow users to view their own permissions


This example shows how you might create a policy that allows IAM users to view the inline and managed policies that are attached to their user identity. This policy includes permissions to complete this action on the console or programmatically using the Amazon CLI or Amazon API.

```
{
    "Version": "2012-10-17",		 	 	 
    "Statement": [
        {
            "Sid": "ViewOwnUserInfo",
            "Effect": "Allow",
            "Action": [
                "iam:GetUserPolicy",
                "iam:ListGroupsForUser",
                "iam:ListAttachedUserPolicies",
                "iam:ListUserPolicies",
                "iam:GetUser"
            ],
            "Resource": ["arn:aws-cn:iam::*:user/${aws:username}"]
        },
        {
            "Sid": "NavigateInConsole",
            "Effect": "Allow",
            "Action": [
                "iam:GetGroupPolicy",
                "iam:GetPolicyVersion",
                "iam:GetPolicy",
                "iam:ListAttachedGroupPolicies",
                "iam:ListGroupPolicies",
                "iam:ListPolicyVersions",
                "iam:ListPolicies",
                "iam:ListUsers"
            ],
            "Resource": "*"
        }
    ]
}
```

## Accessing the Amazon Health Dashboard and the Amazon Health API


The Amazon Health Dashboard is available for all Amazon accounts. The Amazon Health API is available only to accounts with a Amazon Business Support\$1, Amazon Enterprise Support, or Amazon Unified Operations plan. For more information, see [Amazon Web Services Support](https://aws.amazon.com/premiumsupport/).

You can use IAM to create entities (users, groups, or roles), and then give those entities permissions to access the Amazon Health Dashboard and the Amazon Health API.

By default, IAM users don't have access to the Amazon Health Dashboard or the Amazon Health API. You give users access to your account's Amazon Health information by attaching IAM policies to a single user, a group of users, or a role. For more information, see [Identities (Users, Groups, and Roles)](https://docs.amazonaws.cn/IAM/latest/UserGuide/id.html) and [Overview of IAM Policies](https://docs.amazonaws.cn/IAM/latest/UserGuide/PoliciesOverview.html).

After you create IAM users, you can give those users individual passwords. Then, they can sign in to your account and view Amazon Health information by using an account-specific sign-in page. For more information, see [How Users Sign In to Your Account](https://docs.amazonaws.cn/IAM/latest/UserGuide/getting-started_how-users-sign-in.html).

**Note**  
An IAM user with permissions to view Amazon Health Dashboard has read-only access to health information across all Amazon services on the account, which can include, but is not limited to, Amazon resource IDs such as Amazon EC2 instance IDs, EC2 instance IP addresses, and general security notifications.   
For example, if an IAM policy grants access only to Amazon Health Dashboard and the Amazon Health API, then the user or role that the policy applies to can access all information posted about Amazon services and related resources, even if other IAM policies don't allow that access.
+ Individual accounts – You can use the operations such as [DescribeEvents](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeEvents.html) and [DescribeEventDetails](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeEventDetails.html) to get information about Amazon Health events for your account. 
+ Organizational account – You can use operations such as [DescribeEventsForOrganization](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeEventsForOrganization.html) and [DescribeEventDetailsForOrganization](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeEventDetailsForOrganization.html) to get information about Amazon Health events for accounts that are part of your organization.

For more information about the available API operations, see the [Amazon Health API Reference](https://docs.amazonaws.cn/health/latest/APIReference/).

### Individual actions


#### Describe access


This policy statement grants access to Amazon Health Dashboard and any of the `Describe*` Amazon Health API operations. For example, an IAM user with this policy can access the Amazon Health Dashboard in the Amazon Web Services Management Console and call the Amazon Health `DescribeEvents` API operation.

**Example : Describe access**    
****  

```
{
  "Version":"2012-10-17",		 	 	 
  "Statement": [
  {
    "Effect": "Allow",
    "Action": [
      "health:Describe*"
    ],
    "Resource": "*"
  }]
}
```

#### Deny access


This policy statement denies access to Amazon Health Dashboard and the Amazon Health API. An IAM user with this policy can't view the Amazon Health Dashboard in the Amazon Web Services Management Console and can't call any of the Amazon Health API operations.

**Example : Deny access**    
****  

```
{
  "Version":"2012-10-17",		 	 	 
  "Statement": [
  {
    "Effect": "Deny",
    "Action": [
      "health:*"
    ],
    "Resource": "*"
  }]
}
```

### Organizational view


 If you want to enable organizational view for Amazon Health, you must allow access to the Amazon Health and Amazon Organizations actions. 

The `Action` element of an IAM policy must include the following permissions:
+ `iam:CreateServiceLinkedRole`
+ `organizations:EnableAWSServiceAccess`
+ `organizations:DescribeAccount`
+ `organizations:DisableAWSServiceAccess`
+ `organizations:ListAccounts`
+ `organizations:ListDelegatedAdministrators`
+ `organizations:ListParents`

To understand the exact permissions needed for each APIs, see [Actions Defined by Amazon Health APIs and Notifications](https://docs.amazonaws.cn/IAM/latest/UserGuide/list_awshealthapisandnotifications.html#awshealthapisandnotifications-actions-as-permissions) in the *IAM User Guide*.

**Note**  
You must use credentials from the management account for an organization to access the Amazon Health APIs for Amazon Organizations. For more information, see [Aggregating Amazon Health events across accounts](aggregate-events.md).

#### Allow access to Amazon Health organizational view


This policy statement grants access to all Amazon Health and Amazon Organizations actions that you need for the organizational view feature.

**Example : Allow Amazon Health organizational view access**    
****  

```
{
    "Version":"2012-10-17",		 	 	 
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "organizations:EnableAWSServiceAccess",
                "organizations:DisableAWSServiceAccess"
            ],
            "Resource": "*",
            "Condition": {
                "StringEquals": {
                    "organizations:ServicePrincipal": "health.amazonaws.com"
                }
            }
        },
        {
            "Effect": "Allow",
            "Action": [
                "health:*",
                "organizations:DescribeAccount",
                "organizations:ListAccounts",
                "organizations:ListDelegatedAdministrators",  
                "organizations:ListParents"
            ],
            "Resource": "*"
        },
        {
            "Effect": "Allow",
            "Action": "iam:CreateServiceLinkedRole",
            "Resource": "arn:aws-cn:iam::*:role/aws-service-role/health.amazonaws.com/AWSServiceRoleForHealth*"
        }
    ]
}
```

#### Deny access to Amazon Health organizational view


This policy statement denies access to the Amazon Organizations actions but allows access to the Amazon Health actions for an individual account. 

**Example : Deny Amazon Health organizational view access**    
****  

```
{
    "Version":"2012-10-17",		 	 	 
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "health:*"
            ],
            "Resource": "*"
        },
        {
            "Effect": "Deny",
            "Action": [
                "organizations:EnableAWSServiceAccess",
                "organizations:DisableAWSServiceAccess"
            ],
            "Resource": "*",
            "Condition": {
                "StringEquals": {
                    "organizations:ServicePrincipal": "health.amazonaws.com"
                }
            }
        },
        {
            "Effect": "Deny",
            "Action": [
                "organizations:DescribeAccount",
                "organizations:ListAccounts",
                "organizations:ListDelegatedAdministrators",
                "organizations:ListParents"
            ],
            "Resource": "*"
        },
        {
            "Effect": "Deny",
            "Action": "iam:CreateServiceLinkedRole",
            "Resource": "arn:aws-cn:iam::*:role/aws-service-role/health.amazonaws.com/AWSServiceRoleForHealth*"
        }
    ]
}
```

**Note**  
If the user or group that you want to give permissions to already has an IAM policy, you can add the Amazon Health-specific policy statement to that policy.

## Resource- and action-based conditions


Amazon Health supports [IAM conditions](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html) for the [ DescribeAffectedEntities](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeAffectedEntities.html) and [DescribeEventDetails](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeEventDetails.html) API operations. You can use resource- and action-based conditions to restrict events that the Amazon Health API sends to a user, group, or role. 

To do so, update the `Condition` block of the IAM policy or set the `Resource` element. You can use [String Conditions](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html#Conditions_String) to restrict access based on certain Amazon Health event fields. 

You can use the following fields when you specify an Amazon Health event in your policy:
+ `eventTypeCode`
+ `service`

**Notes**  
The [ DescribeAffectedEntities](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeAffectedEntities.html) and [DescribeEventDetails](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeEventDetails.html) API operations support resource-level permissions. For example, you can create a policy to allow or deny specific Amazon Health events.
The [ DescribeAffectedEntitiesForOrganization](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeAffectedEntitiesForOrganization.html) and [DescribeEventDetailsForOrganization](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeEventDetailsForOrganization.html) API operations don't support resource-level permissions.
For more information, see [Actions, resources, and condition keys for Amazon Health APIs and Notifications](https://docs.amazonaws.cn/service-authorization/latest/reference/list_awshealthapisandnotifications.html) in the *Service Authorization Reference*.

**Example : Action-based condition**  
This policy statement grants access to Amazon Health Dashboard and the Amazon Health `Describe*` API operations, but denies access to any Amazon Health events that relate to Amazon EC2.    
****  

```
{
    "Version":"2012-10-17",		 	 	 
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "health:Describe*",
            "Resource": "*"
        },
        {
            "Effect": "Deny",
            "Action": [
                "health:DescribeAffectedEntities",
                "health:DescribeEventDetails"
            ],
            "Resource": "*",
            "Condition": {
                "StringEquals": {
                    "health:service": "EC2"
                }
            }
        }
    ]
}
```

**Example : Resource-based condition**  
The following policy has the same effect, but uses the `Resource` element instead.    
****  

```
{
  "Version":"2012-10-17",		 	 	 
  "Statement": [
  {
    "Effect": "Allow",
    "Action": [
      "health:Describe*"
    ],
    "Resource": "*"
  },
  {
    "Effect": "Deny",
    "Action": [
      "health:DescribeEventDetails",
      "health:DescribeAffectedEntities"
    ],
    "Resource": "arn:aws-cn:health:*::event/EC2/*/*"
  }]
}
```

**Example : eventTypeCode condition**  
This policy statement grants access to Amazon Health Dashboard and the Amazon Health `Describe*` API operations, but denies access to any Amazon Health events with the `eventTypeCode` that matches `AWS_EC2_*`.    
****  

```
{
    "Version":"2012-10-17",		 	 	 
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "health:Describe*",
            "Resource": "*"
        },
        {
            "Effect": "Deny",
            "Action": [
                "health:DescribeAffectedEntities",
                "health:DescribeEventDetails"
            ],
            "Resource": "*",
            "Condition": {
                "StringLike": {
                    "health:eventTypeCode": "AWS_EC2_*"
                }
            }
        }
    ]
}
```

**Important**  
If you call the [DescribeAffectedEntities](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeAffectedEntities.html) and [DescribeEventDetails](https://docs.amazonaws.cn/health/latest/APIReference/API_DescribeEventDetails.html) operations and don't have permission to access the Amazon Health event, the `AccessDeniedException` error appears. For more information, see [Troubleshooting Amazon Health identity and access](security_iam_troubleshoot.md).

# Troubleshooting Amazon Health identity and access
Troubleshooting

Use the following information to diagnose and fix common issues that you might encounter when working with Amazon Health and IAM.

**Topics**
+ [

## I'm not authorized to perform an action in Amazon Health
](#security_iam_troubleshoot-no-permissions)
+ [

## I'm not authorized to perform iam:PassRole
](#security_iam_troubleshoot-passrole)
+ [

## I want to view my access keys
](#security_iam_troubleshoot-access-keys)
+ [

## I'm an administrator and want to allow others to access Amazon Health
](#security_iam_troubleshoot-admin-delegate)
+ [

## I want to allow people outside of my Amazon account to access my Amazon Health resources
](#security_iam_troubleshoot-cross-account-access)

## I'm not authorized to perform an action in Amazon Health


If the Amazon Web Services Management Console tells you that you're not authorized to perform an action, then you must contact your administrator for assistance. Your administrator is the person that provided you with your user name and password.

The `AccessDeniedException` error appears when a user doesn't have permission to use Amazon Health Dashboard or the Amazon Health API operations.

In this case, the user's administrator must update the policy to allow the user access.

The Amazon Health API requires a Amazon Business Support\$1, Amazon Enterprise Support, or Amazon Unified Operations plan from [Amazon Web Services Support](http://aws.amazon.com/premiumsupport/). If you call the Amazon Health API from an account that doesn't have a Amazon Business Support\$1, Amazon Enterprise Support, or Amazon Unified Operations plan, the following error code is returned: `SubscriptionRequiredException`.

## I'm not authorized to perform iam:PassRole


If you receive an error that you're not authorized to perform the `iam:PassRole` action, your policies must be updated to allow you to pass a role to Amazon Health.

Some Amazon Web Services services allow you to pass an existing role to that service instead of creating a new service role or service-linked role. To do this, you must have permissions to pass the role to the service.

The following example error occurs when an IAM user named `marymajor` tries to use the console to perform an action in Amazon Health. However, the action requires the service to have permissions that are granted by a service role. Mary does not have permissions to pass the role to the service.

```
User: arn:aws-cn:iam::123456789012:user/marymajor is not authorized to perform: iam:PassRole
```

In this case, Mary's policies must be updated to allow her to perform the `iam:PassRole` action.

If you need help, contact your Amazon administrator. Your administrator is the person who provided you with your sign-in credentials.

## I want to view my access keys


After you create your IAM user access keys, you can view your access key ID at any time. However, you can't view your secret access key again. If you lose your secret key, you must create a new access key pair. 

Access keys consist of two parts: an access key ID (for example, `AKIAIOSFODNN7EXAMPLE`) and a secret access key (for example, `wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY`). Like a user name and password, you must use both the access key ID and secret access key together to authenticate your requests. Manage your access keys as securely as you do your user name and password.

**Important**  
Do not provide your access keys to a third party, even to help [find your canonical user ID](https://docs.amazonaws.cn/accounts/latest/reference/manage-acct-identifiers.html#FindCanonicalId). By doing this, you might give someone permanent access to your Amazon Web Services account.

When you create an access key pair, you are prompted to save the access key ID and secret access key in a secure location. The secret access key is available only at the time you create it. If you lose your secret access key, you must add new access keys to your IAM user. You can have a maximum of two access keys. If you already have two, you must delete one key pair before creating a new one. To view instructions, see [Managing access keys](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey) in the *IAM User Guide*.

## I'm an administrator and want to allow others to access Amazon Health


To allow others to access Amazon Health, you must grant permission to the people or applications that need access. If you are using Amazon IAM Identity Center to manage people and applications, you assign permission sets to users or groups to define their level of access. Permission sets automatically create and assign IAM policies to IAM roles that are associated with the person or application. For more information, see [Permission sets](https://docs.amazonaws.cn/singlesignon/latest/userguide/permissionsetsconcept.html) in the *Amazon IAM Identity Center User Guide*.

If you are not using IAM Identity Center, you must create IAM entities (users or roles) for the people or applications that need access. You must then attach a policy to the entity that grants them the correct permissions in Amazon Health. After the permissions are granted, provide the credentials to the user or application developer. They will use those credentials to access Amazon. To learn more about creating IAM users, groups, policies, and permissions, see [IAM Identities](https://docs.amazonaws.cn/IAM/latest/UserGuide/id.html) and [Policies and permissions in IAM](https://docs.amazonaws.cn/IAM/latest/UserGuide/access_policies.html) in the *IAM User Guide*.

## I want to allow people outside of my Amazon account to access my Amazon Health resources


You can create a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources.

To learn more, consult the following:
+ To learn whether Amazon Health supports these features, see [How Amazon Health works with IAM](security_iam_service-with-iam.md).
+ To learn how to provide access to your resources across Amazon Web Services accounts that you own, see [Providing access to an IAM user in another Amazon Web Services account that you own](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_roles_common-scenarios_aws-accounts.html) in the *IAM User Guide*.
+ To learn how to provide access to your resources to third-party Amazon Web Services accounts, see [Providing access to Amazon Web Services accounts owned by third parties](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html) in the *IAM User Guide*.
+ To learn how to provide access through identity federation, see [Providing access to externally authenticated users (identity federation)](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_roles_common-scenarios_federated-users.html) in the *IAM User Guide*.
+ To learn the difference between using roles and resource-based policies for cross-account access, see [Cross account resource access in IAM](https://docs.amazonaws.cn/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.

# Using service-linked roles for Amazon Health
Using service-linked roles

Amazon Health uses Amazon Identity and Access Management (IAM)[ service-linked roles](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role). A service-linked role is a unique type of IAM role that is linked directly to Amazon Health. Service-linked roles are predefined by Amazon Health and include all the permissions that the service requires to call other Amazon Web Services services for you. 

You can use a service-linked role to set up Amazon Health to avoid manually adding the necessary permissions. Amazon Health defines the permissions of its service-linked roles, and unless defined otherwise, only Amazon Health can assume its roles. The defined permissions include the trust policy and the permissions policy, and that permissions policy can't be attached to any other IAM entity.

## Service-linked role permissions for Amazon Health


Amazon Health has two service-linked roles: 
+ [https://console.amazonaws.cn/iam/home?#/roles/AWSServiceRoleForHealth_Organizations](https://console.amazonaws.cn/iam/home?#/roles/AWSServiceRoleForHealth_Organizations) – This role trusts the Amazon Health (`health.amazonaws.com`) to assume the role to access Amazon Web Services services for you. Attached to this role is the `Health_OrganizationsServiceRolePolicy` Amazon managed policy.
+ [https://console.amazonaws.cn/iam/home?#/roles/AWSServiceRoleForHealth_EventProcessor](https://console.amazonaws.cn/iam/home?#/roles/AWSServiceRoleForHealth_EventProcessor) – This role trusts the Amazon Health service principal (`event-processor.health.amazonaws.com`) to assume the role for you. Attached to this role is the `AWSHealth_EventProcessorServiceRolePolicy` Amazon managed policy. The service principal uses the role to create an Amazon EventBridge managed rule for Amazon Incident Detection and Response. This rule is the infrastructure required in your Amazon Web Services account to deliver alarm state change information from your account to Amazon Health.

For more information about the Amazon managed policies, see [Amazon managed policies for Amazon Health](security-iam-awsmanpol.md).



## Creating a service-linked role for Amazon Health


You don't need to create the AWSServiceRoleForHealth\$1Organizations service-linked role. When you call the [EnableHealthServiceAccessForOrganization](https://docs.amazonaws.cn//health/latest/APIReference/API_EnableHealthServiceAccessForOrganization.html) operation, Amazon Health creates the this service-linked role in the account for you.

You must manually create the AWSServiceRoleForHealth\$1EventProcessor service-linked role in your account. For more information, see [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*.

## Editing a service-linked role for Amazon Health


Amazon Health doesn't allow you to edit the service-linked role. After you create a service-linked role, you can't change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see [Editing a service-linked role](https://docs.amazonaws.cn/IAM/latest/UserGuide/using-service-linked-roles.html#edit-service-linked-role) in the *IAM User Guide*.

## Deleting a service-linked role for Amazon Health


To delete the AWSServiceRoleForHealth\$1Organizations role, you must first call the [DisableHealthServiceAccessForOrganization](https://docs.amazonaws.cn//health/latest/APIReference/API_DisableHealthServiceAccessForOrganization.html) operation. You can then delete the role through the IAM console, IAM API, or Amazon Command Line Interface (Amazon CLI).



To delete the AWSServiceRoleForHealth\$1EventProcessor role, contact Amazon Web Services Support and ask that they offboard your workloads from Amazon Incident Detection and Response. After this process completes, you can then delete either role through the IAM console, IAM API, or Amazon CLI.

### Related information


For more information, see [Using service-linked roles](https://docs.amazonaws.cn/IAM/latest/UserGuide/using-service-linked-roles.html) in the *IAM User Guide*.

# Amazon managed policies for Amazon Health
Amazon managed policies for Amazon Health







An Amazon managed policy is a standalone policy that is created and administered by Amazon. Amazon managed policies are designed to provide permissions for many common use cases so that you can start assigning permissions to users, groups, and roles.

Keep in mind that Amazon managed policies might not grant least-privilege permissions for your specific use cases because they're available for all Amazon customers to use. We recommend that you reduce permissions further by defining [ customer managed policies](https://docs.amazonaws.cn/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#customer-managed-policies) that are specific to your use cases.

You cannot change the permissions defined in Amazon managed policies. If Amazon updates the permissions defined in an Amazon managed policy, the update affects all principal identities (users, groups, and roles) that the policy is attached to. Amazon is most likely to update an Amazon managed policy when a new Amazon Web Services service is launched or new API operations become available for existing services.

For more information, see [Amazon managed policies](https://docs.amazonaws.cn/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) in the *IAM User Guide*.

Amazon Health has the following managed policies.

**Contents**
+ [

## Amazon managed policy: AWSHealth\$1EventProcessorServiceRolePolicy
](#security-iam-awsmanpol-Health_EventProcessorServiceRolePolicy)
+ [

## Amazon managed policy: Health\$1OrganizationsServiceRolePolicy
](#security-iam-awsmanpol-Health_OrganizationsServiceRolePolicy)
+ [

## Amazon managed policy: AWSHealthFullAccess
](#security-iam-awsmanpol-AWSHealthFullAccess)
+ [

## Amazon Health updates to Amazon managed policies
](#security-iam-awsmanpol-updates)

## Amazon managed policy: AWSHealth\$1EventProcessorServiceRolePolicy
AWSHealth\$1EventProcessorServiceRolePolicy

Amazon Health uses the [https://console.amazonaws.cn/iam/home#/policies/arn:aws:iam::aws:policy/aws-service-role/Health_EventProcessorServiceRolePolicy$jsonEditor](https://console.amazonaws.cn/iam/home#/policies/arn:aws:iam::aws:policy/aws-service-role/Health_EventProcessorServiceRolePolicy$jsonEditor) Amazon managed policy. This managed policy is attached to the `AWSServiceRoleForHealth_EventProcessor` service-linked role. The policy allows the service-linked role to complete actions for you. You can't attach this policy to your IAM entities. For more information, see [Using service-linked roles for Amazon Health](using-service-linked-roles.md).

 

The managed policy has the following permissions to allow Amazon Health to access the Amazon EventBridge rule for Amazon Incident Detection and Response.

 

 **Permissions details** 

This policy includes the following permissions.

 

 
+ `events` – Describes and deletes EventBridge rules, and describes and updates the targets for those rules.

------
#### [ JSON ]

****  

```
{
    "Version":"2012-10-17",		 	 	 
    "Statement": [
        {
            "Condition": {
                "StringEquals": {"events:ManagedBy": "event-processor.health.amazonaws.com"}
            },
            "Action": [
                "events:DeleteRule",
                "events:RemoveTargets",
                "events:PutTargets",
                "events:PutRule"
            ],
            "Resource": "*",
            "Effect": "Allow"
        },
        {
            "Action": [
                "events:ListTargetsByRule",
                "events:DescribeRule"
            ],
            "Resource": "*",
            "Effect": "Allow"
        }
    ]
}
```

------

For a list of changes to the policy, see [Amazon Health updates to Amazon managed policies](#security-iam-awsmanpol-updates).

## Amazon managed policy: Health\$1OrganizationsServiceRolePolicy
Health\$1OrganizationsServiceRolePolicy

Amazon Health uses the [https://console.amazonaws.cn/iam/home#/policies/arn:aws:iam::aws:policy/aws-service-role/Health_OrganizationsServiceRolePolicy$jsonEditor](https://console.amazonaws.cn/iam/home#/policies/arn:aws:iam::aws:policy/aws-service-role/Health_OrganizationsServiceRolePolicy$jsonEditor) Amazon managed policy. This managed policy is attached to the `AWSServiceRoleForHealth_Organizations` service-linked role. The policy allows the service-linked role to complete actions for you. You can't attach this policy to your IAM entities. For more information, see [Using service-linked roles for Amazon Health](using-service-linked-roles.md).

This policy grants permissions that allow Amazon Health to access required Amazon Organizations details for the Health Organizational view.

 **Permissions details** 

This policy includes the following permissions.

 

 
+ `organizations` – Describes the accounts in Amazon Organizations and the Amazon Web Services services that can be used with Organizations.

------
#### [ JSON ]

****  

```
{
    "Version":"2012-10-17",		 	 	 
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "organizations:ListAccounts",
                "organizations:ListAWSServiceAccessForOrganization",
                "organizations:ListDelegatedAdministrators",
                "organizations:DescribeOrganization",
                "organizations:DescribeAccount"
            ],
            "Resource": "*"
        }
    ]
}
```

------

For a list of changes to the policy, see [Amazon Health updates to Amazon managed policies](#security-iam-awsmanpol-updates).

## Amazon managed policy: AWSHealthFullAccess
AWSHealthFullAccess

Amazon Health uses the [https://console.amazonaws.cn//iam/home?#/policies/arn:aws:iam::aws:policy/AWSHealthFullAccess$jsonEditor](https://console.amazonaws.cn//iam/home?#/policies/arn:aws:iam::aws:policy/AWSHealthFullAccess$jsonEditor) Amazon managed policy. The policy grants entities (IAM users or roles) access to the Amazon Health console. For more information, see [Using the Amazon Health console](security_iam_id-based-policy-examples.md#security_iam_id-based-policy-examples-console).

 **Permissions details** 

This policy includes the following permissions.

 

 
+ `organizations` – Enable or disable the Amazon Health organizational view feature for all accounts in an Amazon organization, and view the organizational units (OU) of the management account
+ `health` – Access to the Amazon Health API operations and notifications
+ `iam` – Creates an IAM role that is linked the Amazon Health service

------
#### [ JSON ]

****  

```
{
    "Version":"2012-10-17",		 	 	 
        "Statement": [
            {
                "Sid": "OrganizationWriteAccess",
                "Effect": "Allow",
                "Action": [
                    "organizations:EnableAWSServiceAccess",
                    "organizations:DisableAWSServiceAccess"
                ],
                "Resource": "*",
                "Condition": {
                    "StringEquals": {
                        "organizations:ServicePrincipal": "health.amazonaws.com"
                    }
                }
            },
            {
                "Sid": "HealthFullAccess",
                "Effect": "Allow",
                "Action": [
                    "health:*",
                    "organizations:DescribeAccount",
                    "organizations:ListAccounts",
                    "organizations:ListDelegatedAdministrators",
                    "organizations:ListParents"
                ],
                "Resource": "*"
            },
            {
                "Sid": "ServiceLinkAccess",
                "Effect": "Allow",
                "Action": "iam:CreateServiceLinkedRole",
                "Resource": "*",
                "Condition": {
                    "StringEquals": {
                        "iam:AWSServiceName": "health.amazonaws.com"
                    }
                }
            }
        ]
}
```

------

For a list of changes to the policy, see [Amazon Health updates to Amazon managed policies](#security-iam-awsmanpol-updates).









## Amazon Health updates to Amazon managed policies
Policy updates



View details about updates to Amazon managed policies for Amazon Health since this service began tracking these changes. For automatic alerts about changes to this page, subscribe to the RSS feed on the [Document history for Amazon Health](doc-history.md) page.



The following table describes important updates to the Amazon Health managed policies since January 13, 2022.


**Amazon Health**  

| Change | Description | Date | 
| --- | --- | --- | 
|  [Amazon managed policy: AWSHealthFullAccess](#security-iam-awsmanpol-AWSHealthFullAccess) - Update to an existing policy  |  Amazon Health has expanded the AWSHealthFullAccess policy to Amazon GovCloud (US) Regions and China Regions.  |  October 16, 2023  | 
|  [Amazon managed policy: Health\$1OrganizationsServiceRolePolicy](#security-iam-awsmanpol-Health_OrganizationsServiceRolePolicy) - Update to an existing policy  |  Amazon Health added new Amazon Organizations actions to allow service-linked role to describe the accounts and Amazon services that can be used with Amazon Organizations.  |  July 19, 2023  | 
|  Change log published  |  Change log for the Amazon Health managed policies.  | January 13, 2023 |