AWS res documentation change
Summary
Updated example bucket name in data exfiltration prevention policy from 'mybucket' to 'amzn-s3-demo-bucket'
Security assessment
Change standardizes example bucket name but does not alter security guidance. The documentation already addressed security controls for data exfiltration prevention; this is a documentation consistency improvement rather than a security-related update.
Diff
diff --git a/res/archive/release-minus-1/ug/S3-buckets-preventing-exfiltration.md b/res/archive/release-minus-1/ug/S3-buckets-preventing-exfiltration.md index 229f04100..7cf2edac1 100644 --- a//res/archive/release-minus-1/ug/S3-buckets-preventing-exfiltration.md +++ b//res/archive/release-minus-1/ug/S3-buckets-preventing-exfiltration.md @@ -39 +39 @@ To prevent users from exfiltrating data from secure S3 buckets into their own S3 - 2. In the policy editor, enter a policy that restricts access to resources within your account or a specific account. Here's an example policy (replace `mybucket` with your S3 bucket name and `111122223333` and `444455556666` with the appropriate AWS account IDs that you want to have access): + 2. In the policy editor, enter a policy that restricts access to resources within your account or a specific account. Here's an example policy (replace `amzn-s3-demo-bucket` with your S3 bucket name and `111122223333` and `444455556666` with the appropriate AWS account IDs that you want to have access):