Amazon S3 Bucket Names Aren’t Always Globally Unique Anymore — Here’s What Changed (and Why I’m Excited)

I still remember the first time S3 humbled me. I was following a “hello AWS” tutorial, feeling confident, and then S3 hit me with: Bucket name already exists I tried again. And again. And again. Different names, different variations, still taken! That’s when I learned the “classic rule”: S3 bucket names are globally unique (within an AWS partition). Meaning: if someone anywhere already owns that bucket name, you can’t have it. But here’s the big update I recently learned, and it’s huge for builders, platform teams, and security folks: Amazon S3 now supports creating general-purpose buckets inside an “account regional namespace”, which removes the “find a globally unique name” pain. AWS announced this on Mar 12, 2026: https://aws.amazon.com/about-aws/whats-new/2026/03/amazon-s3-account-regional-namespaces/ In this article, I’ll break down what changed, how it works, why it matters, and how I’d explain it if I were designing bucket naming at scale. What used to be true (and is still true