AWS AmazonS3 documentation change
Summary
Updated event notification structure to version 2.4, unifying all event types under a single version. Added details about new fields (objectAnnotation and hasObjectAnnotation) and updated versioning policy.
Security assessment
The changes describe structural updates to event notification formats without addressing vulnerabilities or weaknesses. No security fixes or mitigations are mentioned.
Diff
diff --git a/AmazonS3/latest/userguide/notification-content-structure.md b/AmazonS3/latest/userguide/notification-content-structure.md index 2bb45e1bb..328ada77e 100644 --- a//AmazonS3/latest/userguide/notification-content-structure.md +++ b//AmazonS3/latest/userguide/notification-content-structure.md @@ -15 +15,3 @@ For a general overview and instructions on configuring event notifications, see -This example shows _version 2.1_ of the event notification JSON structure. Amazon S3 uses _versions 2.1_ , _2.2_ , and _2.3_ of this event structure. Amazon S3 uses version 2.2 for cross-Region replication event notifications. It uses version 2.3 for S3 Lifecycle, S3 Intelligent-Tiering, object ACL, object tagging, and object restoration delete events. These versions contain extra information specific to these operations. Versions 2.2 and 2.3 are otherwise compatible with version 2.1, which Amazon S3 currently uses for all other event notification types. +This example shows _version 2.4_ of the event notification JSON structure. Starting with version 2.4, Amazon S3 uses a single unified version for all event types. Each event contains extra information specific to the operation. Previously, Amazon S3 used version 2.1 for general events, version 2.2 for cross-Region replication events, and version 2.3 for S3 Lifecycle, S3 Intelligent-Tiering, object ACL, object tagging, and object restoration delete events. + +Prior to version 2.4, different event types used different versions of the event notification structure (2.1, 2.2, 2.3). Starting with version 2.4, all event types use a single, unified version. Going forward, the event version is incremented consistently across all event types whenever the schema evolves. @@ -21 +23 @@ This example shows _version 2.1_ of the event notification JSON structure. Amazo - "eventVersion":"2.1", + "eventVersion":"2.4", @@ -70,3 +72 @@ The major version is incremented if Amazon S3 makes a change to the event struct -The minor version is incremented if Amazon S3 adds new fields to the event structure. This might occur if new information is provided for some or all existing events. This might also occur if new information is provided only for newly introduced event types. To stay compatible with new minor versions of the event structure, we recommend that your applications ignore new fields. - -If new event types are introduced, but the structure of the event is otherwise unmodified, the event version doesn't change. +The minor version is incremented if Amazon S3 makes a backward-compatible change to the event structure. This includes adding new fields to the event structure or introducing new event types. To stay compatible with new minor versions of the event structure, we recommend that your applications ignore new fields. @@ -105,0 +106,4 @@ Note the following: + * The `objectAnnotation` key value is only visible for annotation events (`ObjectAnnotation:Put` and `ObjectAnnotation:Delete`). It contains an array with the annotation `name`, `size` (Put events only), and `eTag` (Put events only). + + * For `ObjectCreated:Copy` events, the `object` block includes a `hasObjectAnnotation` boolean field that indicates whether the copied object has annotations. + @@ -139 +143 @@ The following is an example of a message that Amazon S3 sends to publish an `s3: - "eventVersion":"2.1", + "eventVersion":"2.4",