Is the S3 “US Standard” region the same as “us-east-1” in EC2?

Question

I am planning on running a script located on an EC2 instance in us-east-1d.

The script basically pulls in images from a few different places and will th

Answer 1

US standard includes us-east and part of us-west (oregon). It's a legacy construct that only applies for S3

Answer 2

Just to keep it really clear, from official AWS S3 FAQ: https://aws.amazon.com/s3/faqs/

Q. Wasn’t there a US Standard region?

We renamed the US Standard Region to US East (Northern Virginia) Region to be consistent with AWS regional naming conventions. There is no change to the endpoint and you do not need to make any changes to your application.

So yes, us-east-1 is the same.

Answer 3

"US Standard" means "us-east-1".

According to S3 Pricing FAQ

There is no Data Transfer charge for data transferred between Amazon EC2 and Amazon S3 within the same Region or for data transferred between the Amazon EC2 Northern Virginia Region and the Amazon S3 US Standard Region.

This will mean that if your instance is in any of the us-east-1 AZs and your bucket is in the US Standard region, any movement of data between the 2 should cost nothing.

Also, depending on your use case, you may want to look at the new AWS SDK for JavaScript in the Browser as it may offer the direct to S3 uploads you're looking for.

Answer 4

Here's a table from Amazon captured December 2016 (http://docs.aws.amazon.com/ElasticMapReduce/latest/DeveloperGuide/emr-plan-region.html). There is a vast set of more detailed endpoint mappings here: http://docs.aws.amazon.com/general/latest/gr/rande.html.