jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Gaul (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (JCLOUDS-1213) S3: Region is not respected
Date Thu, 12 Jan 2017 06:55:52 GMT

     [ https://issues.apache.org/jira/browse/JCLOUDS-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andrew Gaul resolved JCLOUDS-1213.
       Resolution: Fixed
    Fix Version/s: 2.0.1

> 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
>            Assignee: Timur Alperovich
>              Labels: aws-s3
>             Fix For: 2.1.0, 2.0.1
> 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
> 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

View raw message