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

[Sammaye]

I got this problem while using the S3 client through the AWS factory like:

    $this->aws=Aws::factory(array(
        'key' => $this->key,
        'secret' => $this->secret,
        'region' => Region::US_WEST_2                   
    ));
    return $this->aws->get('s3');

After much investigation (namely this thread: tpyo/amazon-s3-php-class#46 ) I decided it was down to specific region.

I could not change the endpoint directly so I mimicked the default region using:

$s3->setRegion('us-east-1');

And it worked again.

Is this a bug? I have noticed that bucket no longer needs regions, my bucket is a very old one so it is not new.

[mtdowling]

This is an issue with your client configuration settings. You are attempting to access a bucket in a different region than the region setting configured with your client. If you will be working with buckets across multiple regions using the same client, then you should either omit a region setting or use "us-east-1" as you discovered.

[Sammaye]

Though if buckets no longer need regions (my bucket was in us-west-2 originally and my old code, on the original API, uses it there) then isn't the clients setting of region on the S3Client a bug?

[mtdowling]

Are you saying that you are getting this error when using the us-west-2 region accessing a bucket in the us-west-2 region? Can you confirm that the bucket is located in us-west-2? What's the name of your bucket?

[Sammaye]

I have just checked some code: https://github.com/Sammaye/aws_worker/blob/master/encoder.php#L17 that works on the old API wth the same value for the bucket url videos.stagex.co.uk.

It seems that is was working globally without a region

[mtdowling]

That's what I was saying when I said you can either omit the region setting or use us-east-1 to use the global region. It sounds like you might be referencing the bucket using a client that is configured to send requests to a region that is not the same region as the bucket. Judging from your bucket name, I'd guess it's in eu-west-1.

[Sammaye]

So even if all my other stuff is in us-west-2 and s3buckets don't use regions anymore this shouldnt be changed so s3buckets dont take the region into account? Because I cannot find anyway to make a region specific bucket that's why I carried on this thread.

It seems like functionality that could be removed.

[Sammaye]

well you say it might in west-1 but my URL to view buckets is actually: https://console.aws.amazon.com/s3/home?region=us-west-2 and I remember making it there to make the transfer between my SQS queues and other components, including ec2 (in the same region) as fast as possible.

[Sammaye]

Wait no I am an idiot, it was never like that. I remember now, it was only US/EU etc buckets.

Ok ignore me on that, though considering the new behaviour of buckets it does seem that this is functionality that could be removed still and buckets shouldnt take the clients region.

[mtdowling]

Thanks for checking.

It's actually sometimes required to use a region specific endpoint when accessing new buckets before the DNS records have propagated across all regions.

[Sammaye]

Ok Kool thanks for the help :)