AWS AmazonS3 documentation change

Service: AmazonS3 · 2025-08-10 · Documentation medium

File: AmazonS3/latest/userguide/security-best-practices.md

Summary

Added guidance about creating unpredictable bucket names and recommendations against bucket deletion

Security assessment

Provides security recommendations to prevent bucket name reuse and accidental data exposure, but does not indicate a specific security vulnerability being patched.

Diff

diff --git a/AmazonS3/latest/userguide/security-best-practices.md b/AmazonS3/latest/userguide/security-best-practices.md
index 9563aad84..2ebd72174 100644
--- a//AmazonS3/latest/userguide/security-best-practices.md
+++ b//AmazonS3/latest/userguide/security-best-practices.md
@@ -99,0 +100,11 @@ For more information, see [Identity and Access Management for Amazon S3](./secur
+Create bucket names that aren't predictable**
+    
+
+Bucket names must be unique across all AWS accounts in all of the AWS Regions within a partition. Once an AWS account creates a bucket, that bucket name can't be used by another AWS account in the same partition until the bucket is deleted.
+
+We recommend that you create bucket names that aren't predictable. Don't write code that assumes your chosen bucket name is available unless you have already created the bucket. One method for creating bucket names that aren't predictable is to append a Globally Unique Identifier (GUID) to your bucket name, for example, `amazon-s3-demo-bucket-a1b2c3d4-5678-90ab-cdef-example11111`. For more information, see [Creating a bucket that uses a GUID in the bucket name](./bucketnamingrules.html#create-bucket-name-guid).
+
+We recommend that you don't delete your buckets. All AWS Accounts now have a default bucket quota of 10,000 buckets, reducing the need to delete empty buckets from your account. If you delete a bucket, be aware that another AWS account in the same partition can use the same bucket name for a new bucket and can therefore potentially receive requests that are intended for the deleted bucket. If you want to prevent this, or if you want to continue to use the same bucket name, don't delete the bucket. We recommend that you empty the bucket and keep it. Instead of deleting the bucket, block any bucket requests as needed. For buckets no longer in active use, we recommend emptying the bucket of all objects to minimize costs while retaining the bucket itself. For more information, see [Deleting a general purpose bucket](./delete-bucket.html).
+
+**
+