Answers.Body: <p>There are a few regions that support only S3's v4 of signing requests without the possibility of falling back to v2.  The S3 library that Craft 2 uses only supports S3 v2. Check <a href="http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region" rel="nofollow noreferrer">this table</a> for reference - if it says "Version 4 only" in the last column then that region can't be used in Craft 2.</p>
  
  <p>We're not switching out that library in Craft 2.x, but it won't be a problem in Craft 3, so currently your best bet is to move your bucket to a different region, which also supports S3 v2 signing of requests (any other one, really).</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-12-31T15:25:17.463Z
Answers.Text: Haha. Figures I managed to pick the only region that doesn't work. Changed to another region and it works now. Thanks.
Answers.UserDisplayName: peirix
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-15T15:33:50.930Z
Answers.Text: @andris-sevcenko more than a year later and I still run into this problem. When will Frankfurt be supported?
Answers.UserDisplayName: Florian
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-15T19:58:59.227Z
Answers.Text: @Florian the answer is still the same - Craft 3. It's not that simple to switch out a 3rd party lib, especially that complex, so this will definitely not happen in Craft 2.
Answers.UserDisplayName: Andris Sevcenko
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-16T06:30:22.237Z
Answers.Text: So how's 3 coming along? ;)
Answers.UserDisplayName: Florian
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-16T16:55:36.470Z
Answers.Text: @Florian haha, same deal as before - shooting for this year! ;)
Answers.UserDisplayName: Andris Sevcenko
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-03T20:06:04.970Z
Answers.Text: Damm what a bummer ... unfortunately out of various reasons it's not an option for us to switch to another region :( Is there any manual workaround that we could apply?
Answers.UserDisplayName: m9dfukc
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-11-30T18:04:28.790Z
Answers.Text: Note, that this is also a problem with the new Ohio region.
Answers.UserDisplayName: Trevor Davis
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-07T13:10:10.527Z
Answers.Text: I can confirm this is also a problem with the London region. Ireland is okay.
Answers.UserDisplayName: Clive Portman
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-07-19T15:27:17.217Z
Answers.Text: It would be helpful if this was mentioned in the Craft docs. Including some specific error logging (or validation when adding the assets config) would be even better still.
Answers.UserDisplayName: Dom Stubbs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-12-31T14:24:30.337Z
Answers.LastActivityDate: 2017-07-18T11:02:13.020Z
Answers.LastEditDate: 2017-07-18T11:02:13.020Z
Answers.UserDisplayName: Andris Sevcenko
Body: <p>I've just set up a new S3 account and want to move my assets folders there. But when I try to upload a file, I get the following error:</p>
  
  <pre><code>S3::getObjectInfo(mikkelbang, shallowtree.png): [400] Unexpected HTTP status
  </code></pre>
  
  <p>And the same goes for when I try to update the Assets index:</p>
  
  <pre><code>S3::getBucket(): [InvalidRequest] The authorization mechanism you have provided is not supported.
  Please use AWS4-HMAC-SHA256.
  </code></pre>
  
  <p>I've never used S3 before, so it might be something I need to set up there. But I couldn't find any documentation on setting up S3 with Craft...</p>
  
Tags: <assets><s3>
Title: Errors occuring with Assets and Amazon S3
ThreadText: # Errors occuring with Assets and Amazon S3
  
  (Asked by: username_0 on 2014-12-31)
  
  I've just set up a new S3 account and want to move my assets folders there. But when I try to upload a file, I get the following error:
  
  ```
  S3::getObjectInfo(mikkelbang, shallowtree.png): [400] Unexpected HTTP status
  
  ```
  
  And the same goes for when I try to update the Assets index:
  
  ```
  S3::getBucket(): [InvalidRequest] The authorization mechanism you have provided is not supported.
  Please use AWS4-HMAC-SHA256.
  
  ```
  
  I've never used S3 before, so it might be something I need to set up there. But I couldn't find any documentation on setting up S3 with Craft...
  
  **Tags:** assets, s3
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-12-31. Score: 12 | Accepted answer
  
  There are a few regions that support only S3's v4 of signing requests without the possibility of falling back to v2. The S3 library that Craft 2 uses only supports S3 v2. Check [this table](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region) for reference - if it says "Version 4 only" in the last column then that region can't be used in Craft 2.
  
  We're not switching out that library in Craft 2.x, but it won't be a problem in Craft 3, so currently your best bet is to move your bucket to a different region, which also supports S3 v2 signing of requests (any other one, really).
  
  > **Comments:**
  > **username_0**: Haha. Figures I managed to pick the only region that doesn't work. Changed to another region and it works now. Thanks.  
  > **username_2**: @username_1-username_1 more than a year later and I still run into this problem. When will Frankfurt be supported?  
  > **username_1**: @username_2 the answer is still the same - Craft 3. It's not that simple to switch out a 3rd party lib, especially that complex, so this will definitely not happen in Craft 2.  
  > **username_2**: So how's 3 coming along? ;)  
  > **username_1**: @username_2 haha, same deal as before - shooting for this year! ;)  
  > **username_3**: Damm what a bummer ... unfortunately out of various reasons it's not an option for us to switch to another region :( Is there any manual workaround that we could apply?  
  > **username_4**: Note, that this is also a problem with the new Ohio region.  
  > **username_5**: I can confirm this is also a problem with the London region. Ireland is okay.  
  > **username_6**: It would be helpful if this was mentioned in the Craft docs. Including some specific error logging (or validation when adding the assets config) would be even better still.  
  
  ---
  
  