AWS eventbridge documentation change
Summary
Updated terminology from 'events' to 'resources' in key retention guidance and section headers
Security assessment
The changes clarify key management practices but do not introduce new security concepts or address specific security issues
Diff
diff --git a/eventbridge/latest/userguide/eb-encryption-event-bus-key-managment.md b/eventbridge/latest/userguide/eb-encryption-event-bus-key-managment.md index cfb4d7207..b45f728f7 100644 --- a//eventbridge/latest/userguide/eb-encryption-event-bus-key-managment.md +++ b//eventbridge/latest/userguide/eb-encryption-event-bus-key-managment.md @@ -9 +9 @@ To ensure EventBridge always retains access to the necessary customer managed ke - * Do not delete a customer managed key until you are sure all events encrypted with it have been processed. + * Do not delete a customer managed key until you are sure all resources encrypted with it have been processed. @@ -11 +11 @@ To ensure EventBridge always retains access to the necessary customer managed ke -When you perform any of the following operations, retain the previous key material to ensure EventBridge can continue to use it for previously-encrypted events: +When you perform any of the following operations, retain the previous key material to ensure EventBridge can continue to use it for previously-encrypted resources: @@ -43 +43 @@ Authorizing key use -Encrypting events +Encrypting event buses