AWS notifications documentation change
Summary
Added clarification about managed notification requirements and deduplication scope
Security assessment
Changes clarify operational requirements but don't address security vulnerabilities or document security features.
Diff
diff --git a/notifications/latest/userguide/managed-notification-aggregation.md index 56ff2a786..a4f3e53eb 100644 --- a/notifications/latest/userguide/managed-notification-aggregation.md +++ b/notifications/latest/userguide/managed-notification-aggregation.md @@ -12,0 +13,4 @@ In addition, User Notifications deduplicates emails when an account contact is s +###### Note + +Aggregation only requires the management account (or delegated administrator) to enable managed notifications. Deduplication requires both the management account and member accounts to enable managed notifications. For more information, see [Enabling or disabling AWS managed notifications for AWS Health in AWS User Notifications](./managing-notification-features.html). + @@ -28 +32 @@ Aggregation behavior is identical for both the management account and delegated -User Notifications deduplicates event information across account contacts as follows: +When the management and member accounts [enable managed notifications](./managing-notification-features.html), User Notifications deduplicates event information across account contacts as follows: @@ -38,0 +43,2 @@ User Notifications deduplicates event information across account contacts as fol +Deduplication only applies to account contact emails. AWS managed notifications sent to other member account delivery channels (for example, the Notification Center) are always sent. +