AWS data-exchange documentation change
Summary
Updated terminology from 'S3 bucket' to 'Amazon S3 bucket' and added 'Tags' condition to bucket policy example.
Security assessment
The addition of a 'Tags' condition in the bucket policy example demonstrates how to implement tag-based access controls, which is a security-related configuration. However, this is a documentation improvement rather than a response to a specific security issue.
Diff
diff --git a/data-exchange/latest/userguide/auto-export-rev-s3-console-sub.md b/data-exchange/latest/userguide/auto-export-rev-s3-console-sub.md index dd4d6d732..c14b6d593 100644 --- a//data-exchange/latest/userguide/auto-export-rev-s3-console-sub.md +++ b//data-exchange/latest/userguide/auto-export-rev-s3-console-sub.md @@ -28 +28 @@ To automatically export revisions to an S3 bucket of your choice, your S3 bucket -Before you can automatically export revisions to an S3 bucket, you must disable requester pays and your S3 bucket must have a bucket policy with permissions set to allow AWS Data Exchange to export data into it. The following procedures provide information about how to either edit your existing S3 bucket policy or create an S3 bucket policy with these permissions. +Before you can automatically export revisions to an Amazon S3 bucket, you must disable requester pays and your Amazon S3 bucket must have a bucket policy with permissions set to allow AWS Data Exchange to export data into it. The following procedures provide information about how to either edit your existing S3 bucket policy or create an S3 bucket policy with these permissions. @@ -206,0 +207,2 @@ To automatically export revisions to an S3 bucket of your choice, your S3 bucket + * `Tags` +