SignatureDoesNotMatch about aws HOT 13 CLOSED

Could you please provide a minimal test case? It seems to be working for me flawlessly.

from aws.

I use your library inside Yesod. Please look at code here http://paste.org/48583.

Also i make requests from ubuntu installed on virtual box.

Thanks.

from aws.

This works just fine for me, of course using a different bucket and a different lazy ByteString.

Is there a proxy? Do you have the most recent versions of aws installed? Did you make modifications to your copy of the aws codebase?

from aws.

I've also tried if maybe a big 20 MB file would present problems. No, works fine.

Sorry, but I really can't replicate this.

from aws.

I installed aws package from hackage without modifications. It was the first installation of aws on my system. I'll try to run this code outside virtualbox for interest and make other experiments.

from aws.

i think have found the bug. It turns out that bucket name in your library must be in lower case . I created the bucket with name in lower case letters "fwbuckettest" and it's work just fine. I don't make sense how it works for you .

from aws.

It works for me, because all my buckets have lower-case names. I suggest that you just write the name in lower-case while we figure out how to deal with this.

from aws.

Oh, by the way: the s3ErrorStringToSign parameter can help identify the problem. We did not have that available though.

from aws.

According to this: http://docs.amazonwebservices.com/AmazonS3/2006-03-01/dev/BucketRestrictions.html

Bucket names are NOT generally case-insensitive, and outside the US Standard region, bucket names must always be lower-case if I understand it right.

@meteficha What do you think?

from aws.

@acheshkov If you actually have upper-case bucket names (which is only allowed in the US Standard region), then switching to PathStyle requests should work. You have to change the S3 configuration for that.

from aws.

AWS themselves say that you have DNS complient bucket names. I guess we should put a note on the docs of aws.

from aws.

@meteficha No, in the US standard region, non-DNS-compliant names are allowed. You have to use path-style requests for those.

I've tested it, and that constraint is enforced. When trying to create a bucket with uppercase characters in the Ireland region, I get this error: "A bucket name in Ireland region must contain only lower case characters"

If we want it to "just work", we might consider to detect upper-case characters and switch the request style for those (by default).

from aws.

Sorry, there should be a "should" on my phrase above. =)

Quoting them: "It is therefore recommended that you always use bucket names that are DNS compliant regardless of the region in which you create the bucket."

from aws.