AWS health documentation change
Summary
Updated documentation to consistently use 'AWS Health Dashboard' instead of 'Health Dashboard' throughout the file
Security assessment
This change is purely a branding/naming consistency update. There is no evidence of addressing a security vulnerability, weakness, or incident. The changes are cosmetic updates to ensure consistent terminology usage. The security implications are neutral; it does not introduce new security guidance or fix existing security issues.
Diff
diff --git a/health/latest/ug/security_iam_id-based-policy-examples.md b/health/latest/ug/security_iam_id-based-policy-examples.md index d06dd8911..43dd40ed2 100644 --- a//health/latest/ug/security_iam_id-based-policy-examples.md +++ b//health/latest/ug/security_iam_id-based-policy-examples.md @@ -5 +5 @@ -Policy best practicesUsing the consoleAllow users to view their own permissionsAccessing the Health Dashboard and the AWS Health APIResource- and action-based conditions +Policy best practicesUsing the consoleAllow users to view their own permissionsAccessing the AWS Health Dashboard and the AWS Health APIResource- and action-based conditions @@ -21 +21 @@ To learn how to create an IAM identity-based policy using these example JSON pol - * Accessing the Health Dashboard and the AWS Health API + * Accessing the AWS Health Dashboard and the AWS Health API @@ -57 +57 @@ The `AWSHealthFullAccess` policy grants an entity full access to the following: - * The Health Dashboard in the AWS Health console + * The AWS Health Dashboard in the AWS Health console @@ -164 +164 @@ This example shows how you might create a policy that allows IAM users to view t -## Accessing the Health Dashboard and the AWS Health API +## Accessing the AWS Health Dashboard and the AWS Health API @@ -166 +166 @@ This example shows how you might create a policy that allows IAM users to view t -The Health Dashboard is available for all AWS accounts. The AWS Health API is available only to accounts with a AWS Business Support+, AWS Enterprise Support, or AWS Unified Operations plan. For more information, see [Support](https://aws.amazon.com/premiumsupport/). +The AWS Health Dashboard is available for all AWS accounts. The AWS Health API is available only to accounts with a AWS Business Support+, AWS Enterprise Support, or AWS Unified Operations plan. For more information, see [Support](https://aws.amazon.com/premiumsupport/). @@ -168 +168 @@ The Health Dashboard is available for all AWS accounts. The AWS Health API is av -You can use IAM to create entities (users, groups, or roles), and then give those entities permissions to access the Health Dashboard and the AWS Health API. +You can use IAM to create entities (users, groups, or roles), and then give those entities permissions to access the AWS Health Dashboard and the AWS Health API. @@ -170 +170 @@ You can use IAM to create entities (users, groups, or roles), and then give thos -By default, IAM users don't have access to the Health Dashboard or the AWS Health API. You give users access to your account's AWS 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.aws.amazon.com/IAM/latest/UserGuide/id.html) and [Overview of IAM Policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/PoliciesOverview.html). +By default, IAM users don't have access to the AWS Health Dashboard or the AWS Health API. You give users access to your account's AWS 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.aws.amazon.com/IAM/latest/UserGuide/id.html) and [Overview of IAM Policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/PoliciesOverview.html). @@ -176 +176 @@ After you create IAM users, you can give those users individual passwords. Then, -An IAM user with permissions to view Health Dashboard has read-only access to health information across all AWS services on the account, which can include, but is not limited to, AWS resource IDs such as Amazon EC2 instance IDs, EC2 instance IP addresses, and general security notifications. +An IAM user with permissions to view AWS Health Dashboard has read-only access to health information across all AWS services on the account, which can include, but is not limited to, AWS resource IDs such as Amazon EC2 instance IDs, EC2 instance IP addresses, and general security notifications. @@ -178 +178 @@ An IAM user with permissions to view Health Dashboard has read-only access to he -For example, if an IAM policy grants access only to Health Dashboard and the AWS Health API, then the user or role that the policy applies to can access all information posted about AWS services and related resources, even if other IAM policies don't allow that access. +For example, if an IAM policy grants access only to AWS Health Dashboard and the AWS Health API, then the user or role that the policy applies to can access all information posted about AWS services and related resources, even if other IAM policies don't allow that access. @@ -193 +193 @@ For more information about the available API operations, see the [AWS Health API -You can set the `Action` element of an IAM policy to `health:Describe*`. This allows access to the Health Dashboard and AWS Health. AWS Health supports access control to events based on the `eventTypeCode` and service. +You can set the `Action` element of an IAM policy to `health:Describe*`. This allows access to the AWS Health Dashboard and AWS Health. AWS Health supports access control to events based on the `eventTypeCode` and service. @@ -197 +197 @@ You can set the `Action` element of an IAM policy to `health:Describe*`. This al -This policy statement grants access to Health Dashboard and any of the `Describe*` AWS Health API operations. For example, an IAM user with this policy can access the Health Dashboard in the AWS Management Console and call the AWS Health `DescribeEvents` API operation. +This policy statement grants access to AWS Health Dashboard and any of the `Describe*` AWS Health API operations. For example, an IAM user with this policy can access the AWS Health Dashboard in the AWS Management Console and call the AWS Health `DescribeEvents` API operation. @@ -223 +223 @@ JSON -This policy statement denies access to Health Dashboard and the AWS Health API. An IAM user with this policy can't view the Health Dashboard in the AWS Management Console and can't call any of the AWS Health API operations. +This policy statement denies access to AWS Health Dashboard and the AWS Health API. An IAM user with this policy can't view the AWS Health Dashboard in the AWS Management Console and can't call any of the AWS Health API operations. @@ -412 +412 @@ You can use the following fields when you specify an AWS Health event in your po -This policy statement grants access to Health Dashboard and the AWS Health `Describe*` API operations, but denies access to any AWS Health events that relate to Amazon EC2. +This policy statement grants access to AWS Health Dashboard and the AWS Health `Describe*` API operations, but denies access to any AWS Health events that relate to Amazon EC2. @@ -480 +480 @@ JSON -This policy statement grants access to Health Dashboard and the AWS Health `Describe*` API operations, but denies access to any AWS Health events with the `eventTypeCode` that matches `AWS_EC2_*`. +This policy statement grants access to AWS Health Dashboard and the AWS Health `Describe*` API operations, but denies access to any AWS Health events with the `eventTypeCode` that matches `AWS_EC2_*`.