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 throw them into an S3 bucket in the US-Standard Region.

Since there is no way to upload directly into an s3 bucket (by sending an API request that causes S3 to fetch a file from a remote URL as written about here and I don't think this has changed) I would like to make sure that the each image I save as temp file on my ec2 will not result in additional bandwidth charges when written to S3 (ie. leaves the Amazon data center). Will a us-east-1d EC2 instance uploading to a US-Standard S3 bucket will be communicating within the same AWS region?

Any insight into this would be greatly appreciated as it will be terabytes of data and I'm on a shoestring bucket I'd like to know before proceeding.

Answer 1

"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 2

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