PermanentRedirect: The bucket you are attempting to access must be addressed using the specified endpoint.

[kerry350]

PermanentRedirect: The bucket you are attempting to access must be addressed using the specified endpoint.

[johnnyshields]

This could be related to the S3 region not being specified (sometimes AWS requires the region explicitly even though it's already in the hostname). I've seen a similar error in a different library.

[timiyay]

@radcliff Did you end up resolving this?

I'm getting a similar issue, and I'm currently assuming I'm misunderstanding the hostName value I'm supposed to use. A quick Google points to this issue being for non-US regions (I'm in ap-southeast-2), but all variations on the hostName are throwing the same error for me.

Am I supposed to be using the full s3 static site host name? (i.e. ember.index.s3-website-ap-southeast-2.amazonaws.com)

Not only does ember deploy:list fail, but so does the index / store deployment. The assets works, but the index bucket is not updated.

UPDATE: some digging showed that my issue occurs when my non-US bucket name has periods in it. This means it's likely related to #25

I'll keep digging, as it appears to be related to aws/aws-sdk-js#285 which, in turn, pushes the blame down to the S3 API.

The requirements of S3 static website hosting, where the bucket name matches the domain name, require periods.

[timiyay]

Solved.

You have to specify region in your config, which is transparently passed down to aws-sdk, which passes it to the S3 API. Otherwise, the region is set as us-east-1, and the redirect comes back.

Example:

store: {
  type: 'S3',
  bucket: 'ember.index',
  accessKeyId: xxxxxxxxxxxxxxx,
  secretAccessKey: xxxxxxxxxxxxxxx,
  hostName: 'ember.index.s3-website-ap-southeast-2.amazonaws.com',
  indexMode: 'direct'
}