AWS health documentation change
Summary
Updated references from 'AWS Health Dashboard' to 'Health Dashboard' and clarified trusted access permissions.
Security assessment
Terminology standardization and permission clarification without new security content or vulnerability references.
Diff
diff --git a/health/latest/ug/manage-user-notifications.md b/health/latest/ug/manage-user-notifications.md index 798653edb..c0c6b70c5 100644 --- a//health/latest/ug/manage-user-notifications.md +++ b//health/latest/ug/manage-user-notifications.md @@ -32 +32 @@ For comprehensive visibility into AWS Health event details, including affected r - * The AWS Health Dashboard + * The Health Dashboard @@ -68 +68 @@ Yes, trusted access with AWS User Notifications from AWS Organizations is requir -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 AWS 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. +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.