Are S3 buckets region specific?

When we go to S3 in AWS console in "Global" option it shows

"S3 does not require region selection."

But when we create new bucket there it asks for Region !

So are S3 buckets region specific ?

The user interface shows all your buckets, in all regions. But buckets exist in a specific region and you need to specify that region when you create a bucket.

S3 buckets are region specific, you can check http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region to get the list of end-points based on the region

From the doc on creating S3 bucket

> Amazon S3 creates bucket in a region you specify. You can choose any > AWS region that is geographically close to you to optimize latency, > minimize costs, or address regulatory requirements. For example, if > you reside in Europe, you might find it advantageous to create buckets > in the EU (Ireland) or EU (Frankfurt) regions. For a list of AWS > Amazon S3 regions, go to Regions and Endpoints in the AWS General > Reference.

Also from UI, if you look at the properties for each of your bucket, you will see the original region

Yes S3 buckets are region specific.

When you create a new bucket you need to select the target region for that bucket.

For example:

Hope it helps.

How it works now is that if you are expecting the content to load fast globally, you create a bucket for every region you want your data to load quickly from, but use 'Versioning' to auto duplicate content from one bucket to the other.

Click on one of your buckets, then go to Management, then go to 'Replication'. Follow the instructions to setup a rule that will copy from one bucket to another.

Congratualtion, you now have globally fast content from a single bucket.

I appreciate if this seems a little off-piste, but I think this is what we are all really looking to achieve.

There is a related answer that highlights one important point: although the console and the CLI allow viewing buckets in all regions, probably due to the fact that bucket names must be globally unique, buckets are still tied to a region.

This matters, for example, when dealing with permissions. You may have Infrastructure as Code generalized with roles that give permissions to all buckets for the current region. Although the CLI might give you the impression that a newly created bucket can be seen in all regions, in reality you may end up with errors if you fail to specifically grant access to a service running in one region but requiring access to an S3 bucket in another region.