AWS notifications: Clarify AWS Health scope and trusted access for notification aggregation
Summary
Rewrites the aggregation section to state that aggregation applies to AWS Health managed notifications across accounts in the same organization, requires the management account or delegated administrator to enable trusted access with AWS Organizations, clarifies email deduplication for shared account contacts, tweaks time-window wording, and fixes the AWS Health EventBridge schema link and heading labels.
Security assessment
The change is editorial and scope-clarifying: it narrows aggregation to AWS Health managed notifications and restates the existing requirement that a management account or delegated administrator enable trusted access with AWS Organizations before cross-account aggregation occurs. No new encryption, authz mechanism, credential handling, CVE, or vulnerability fix is introduced, so security impact is minimal.
Evidence
+You can aggregate AWS Health managed notifications across accounts within the same organization. To use aggregation, your management account or delegated administrator must [enable trusted access](./uno-orgs.html) with AWS Organizations. User Notifications then combines related events from multiple member accounts into a single notification, reducing the total number of notifications you receive.
Diff
diff --git a/notifications/latest/userguide/managed-notification-aggregation.md b/notifications/latest/userguide/managed-notification-aggregation.md index d832f9a92..39ed69e8b 100644 --- a//notifications/latest/userguide/managed-notification-aggregation.md +++ b//notifications/latest/userguide/managed-notification-aggregation.md @@ -9 +9 @@ Event aggregation processAggregating AWS managed notificationsDeduplicating AWS -# Aggregating and deduplicating AWS managed notifications in AWS User Notifications +# Aggregating and deduplicating AWS managed notifications in User Notifications @@ -11 +11 @@ Event aggregation processAggregating AWS managed notificationsDeduplicating AWS -AWS managed notification aggregation is a standard feature available to all management accounts and delegated administrators that have [enabled trusted access](./uno-orgs.html) with AWS Organizations. Managed notification aggregation organizes and streamlines your view of events that impact multiple accounts within an organization. User Notifications uses information from AWS Organizations to aggregate events across accounts within an organization and provides an organized view of events affecting multiple accounts. +You can aggregate AWS Health managed notifications across accounts within the same organization. To use aggregation, your management account or delegated administrator must [enable trusted access](./uno-orgs.html) with AWS Organizations. User Notifications then combines related events from multiple member accounts into a single notification, reducing the total number of notifications you receive. @@ -13 +13 @@ AWS managed notification aggregation is a standard feature available to all mana -In addition, User Notifications deduplicates emails when an account contact is shared between the management account (or delegated administrator) and the member account. This reduces the total number of individual notifications you receive. +For AWS Health managed notifications, User Notifications also deduplicates emails when you share an account contact between the management account (or delegated administrator) and a member account. This reduces the number of individual notifications you receive. @@ -17 +17 @@ In addition, User Notifications deduplicates emails when an account contact is s -AWS managed notifications use an event aggregation logic that combines related events to reduce notification volume while maintaining timely delivery of critical information. Events are aggregated based on two key factors: +AWS managed notifications use an event aggregation logic that combines related events to reduce the number of notifications while maintaining timely delivery of critical information. Events are aggregated based on two key factors: @@ -28 +28 @@ AWS managed notifications use an event aggregation logic that combines related e -Events are sent to User Notifications via an API integration that uses the same format as Amazon EventBridge. For more information, see [Reference: AWS Health events Amazon EventBridge schema](https://docs.aws.amazon.com/health/latest/ug//aws-health-events-eventbridge-schema) in the _AWS Health User Guide_. +Events are sent to User Notifications through an API integration that uses the same format as Amazon EventBridge. For more information, see [Reference: AWS Health events Amazon EventBridge schema](https://docs.aws.amazon.com/health/latest/ug/aws-health-events-eventbridge-schema.html) in the _AWS Health User Guide_. @@ -30 +30 @@ Events are sent to User Notifications via an API integration that uses the same - * Time window - Events with the same `communicationId` are aggregated within specific time periods based on managed notification sub-category: + * Time window - Events with the same `communicationId` are aggregated within specific time periods based on managed notification sub-category. The following table lists the sub-categories and time windows that apply to AWS Health managed notifications. @@ -32 +32 @@ Events are sent to User Notifications via an API integration that uses the same -`Sub-category` | Time window +AWS Health managed notification sub-categories and aggregation time windows `Sub-category` | Time window @@ -80 +80 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Viewing AWS managed notifications +AWS Health notifications @@ -82 +82 @@ Viewing AWS managed notifications -User-configured notifications +AWS Marketplace and AWS Partner Central notifications