You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Halvdan Hoem Grelland (JIRA)" <ji...@apache.org> on 2016/11/28 15:49:58 UTC

[jira] [Created] (JCLOUDS-1213) S3: Region is not respected

Halvdan Hoem Grelland created JCLOUDS-1213:
----------------------------------------------

             Summary: S3: Region is not respected
                 Key: JCLOUDS-1213
                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1213
             Project: jclouds
          Issue Type: Bug
          Components: jclouds-blobstore
    Affects Versions: 2.0.0
            Reporter: Halvdan Hoem Grelland


When using a BlobStore configured for the 'aws-s3' provider and with an explicit region ('eu-west-1' in this case), _BlobStore.createContainerInLocation(Location location, String container)_ fails with a 400 when attempting to create an already existing bucket on that location.

The error message from AWS claims the cause to be _AuthorizationHeaderMalformed_, and says that 'eu-west-1' was expected, but that 'us-east-1' was supplied in the PUT request.

I have confirmed that 'eu-west-1' is, in fact, given to the method call, but it does not seem to be respected when forming and signing the request.

This does not happen on 1.9.x.

From the debugging i have done a likely culprit seems to be _Aws4SignerForAuthorizationHeader_ which resolves a _ServiceAndRegion_ instance, which in turn seem to attempt parsing the region from the hostname URL (_AWSHostNameUtils.parseRegionName(..)_). I cannot see the region set for the provider being respected in this case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)