AWS Security ChangesHomeSearch

AWS ebs documentation change

Service: ebs · 2025-03-19 · Documentation low

File: ebs/latest/userguide/ebs-cloud-watch-events.md

Summary

Updated event trigger condition from successful attach/reattach to failed attach/reattach scenarios

Security assessment

Clarification of event emission conditions without explicit security context

Diff

diff --git a/ebs/latest/userguide/ebs-cloud-watch-events.md b/ebs/latest/userguide/ebs-cloud-watch-events.md
index ca56387c8..766390941 100644
--- a/ebs/latest/userguide/ebs-cloud-watch-events.md
+++ b/ebs/latest/userguide/ebs-cloud-watch-events.md
@@ -151 +151 @@ The listing below is an example of a JSON object emitted by EBS for a successful
-The `attachVolume` or `reattachVolume` event is sent to your AWS account when a volume is attached or reattached to an instance. However, it is not saved, logged, or archived. If you use a KMS key to encrypt an EBS volume and the KMS key becomes invalid, EBS will emit an event if that KMS key is later used to attach or reattach to an instance, as shown in the examples below.
+The `attachVolume` or `reattachVolume` event is sent to your AWS account if a volume fails to attach or reattach to an instance. However, it is not saved, logged, or archived. If you use a KMS key to encrypt an EBS volume and the KMS key becomes invalid, EBS will emit an event if that KMS key is later used to attach or reattach to an instance, as shown in the examples below.