Re: requested location eu-central-1, which is not in the configured locations

I can confirm that the aws-s3 provider still uses the v2 signatures. I committed several fixes for the v4 signatures in JCLOUDS-766 but one blocking issue remains. v4 URL signing requires a content hash for the server to accept the PUT request but the jclouds API does not allow for this. One

Re: requested location eu-central-1, which is not in the configured locations

Hi, I would also like to know how to use AWS S3 v4 signature for authentication. Is there way to specify which signature version to use while constructing a BlobStoreContext? Thanks in advance, Ranjith On Tue, Mar 8, 2016 at 3:24 PM, Archana C wrote: > From the

Re: requested location eu-central-1, which is not in the configured locations

From the amazon documentation, we understand that the region eu-central-1 (Frankfurt) supports only AWS signature version 4, and from  https://issues.apache.org/jira/browse/JCLOUDS-480 we understand the jclouds already has the support added for version 4 signature.  What we are trying to figure

Re: requested location eu-central-1, which is not in the configured locations

Please test again with the latest master which includes a fix: https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=c18371a7 On Mon, Mar 07, 2016 at 12:29:59PM +, Archana C wrote: > public class App > { >     public static void main( String[] args ) throws IOException >     { >  

Re: requested location eu-central-1, which is not in the configured locations

Jclouda version 2.0.0-SNAPSHOT RegardsArc Sent from Yahoo Mail on Android On Mon, Mar 7, 2016 at 7:04 PM, Ignasi Barrera wrote: That region is supported since jclouds 1.9.0. Which version are you using? On 7 March 2016 at 13:29, Archana C wrote: >