The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.

[nodesocket]

The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.

This error happens when attempting to upload to a bucket other than us-standard.

[dekelev]

I've successfully uploaded a test file to 'eu-west-1' region using 'example-form.php' file.
Can you post an example code?

[tpyo]

Unfortunately there is no region detection, so you'd need to call S3::setEndpoint() to access other endpoints first:
S3::setEndpoint('s3-eu-west-1.amazonaws.com');

[dekelev]

From what I know, S3 is cross-region, which means that you do not need to specify a region to upload files to, as it will uploads to one and replicates to other regions behind the scenes. Therefor endpoint = 's3.amazonaws.com'
If your bucket called 'test', you will upload to 'test.s3.amazonaws.com', not to 'test.s3-eu-west-1.amazonaws.com'.

[tpyo]

Seems you could be right about that @dekelev - will need to look into it a little more.

[BWLR]

I can confirm that @tpyo 's suggestion of setting the endpoint manually using the following worked for me.

$s3 = new S3(); $s3->setEndpoint('s3-eu-west-1.amazonaws.com');

(even though I was setting the public static $endpoint = 's3-eu-west-1.amazonaws.com'; in S3.php)

FYI I'm using a bucket in Region: Ireland

[dekelev]

well I read about it here, and under "Regions" it says you do create the S3 bucket in a region and it replictes only within that region, not to other regions, so it make sense to use a region specific domain name.

http://aws.amazon.com/s3/faqs/#Where_is_my_data_stored

[jonathancrane]

I'm coming across a similar issue. So the https://BUCKETNAME.s3.amazonaws.com/PATH/TO/FILE format is region-agnostic, but you have to make sure that the bucket name is DNS compatiable. When you put the request into the above format, what the web server does is convert all letters in the bucket name to lower case. So if the bucket name has upper case letters, you'll get "The specified bucket does not exist."

I do not think that it's coincidental that for regions outside of "US Standard," we can only use numbers and lower case letters in bucket names.

[jonathancrane]

Figured out my issue. My app is in Node and it turns out there's a global config where you specify a region. So you're basically confined to accessing buckets in the stated region. Seems inflexible. Am wondering what the reason behind it is.

[pitashi]

This does appear to matter, at least in my use case. When instantiating the S3 object and trying to use any of the methods if I do not specify the region like this $s3->setEndpoint('s3-us-west-1.amazonaws.com'); it will not work. Specifically noticed this with getObject