Amazon S3 invalid signature

[creztoe]

Im am having trouble generating a valid signature when sending a
request to Amazon S3.
Below is the code snippet used to generate and send the request.

fileName = @"test.caf";
[ASIS3Request setSharedSecretAccessKey:*mySecretKey*];
[ASIS3Request setSharedAccessKey:*myAccessKey*];

NSString *filePath = [NSTemporaryDirectory()
stringByAppendingPathComponent: @"recordedFile.caf"];
ASIS3ObjectRequest *request =
[ASIS3ObjectRequest PUTRequestForFile:filePath
withBucket:@"MarkerAudio" key:fileName];
[request startSynchronous];
if ([request error]) {
NSLog(@"%@",[[request error] localizedDescription]);
}

Error reported is:
The request signature we calculated does not match the signature you
provided. Check your key and signing method.

I have used the same access and secret key to access the bucket
through other means and it works fine. Any help is much appreciated.

--
You received this message because you are subscribed to the Google Groups "ASIHTTPRequest" group.
To post to this group, send email to asihttp...@googlegroups.com.
To unsubscribe from this group, send email to asihttpreques...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/asihttprequest?hl=en.

[Ben Copsey]

Hi

> Im am having trouble generating a valid signature when sending a
> request to Amazon S3.
> Below is the code snippet used to generate and send the request.
>
> fileName = @"test.caf";
> [ASIS3Request setSharedSecretAccessKey:*mySecretKey*];
> [ASIS3Request setSharedAccessKey:*myAccessKey*];
>
> NSString *filePath = [NSTemporaryDirectory()
> stringByAppendingPathComponent: @"recordedFile.caf"];
> ASIS3ObjectRequest *request =
> [ASIS3ObjectRequest PUTRequestForFile:filePath
> withBucket:@"MarkerAudio" key:fileName];
> [request startSynchronous];
> if ([request error]) {
> NSLog(@"%@",[[request error] localizedDescription]);
> }
>
> Error reported is:
> The request signature we calculated does not match the signature you
> provided. Check your key and signing method.
>
> I have used the same access and secret key to access the bucket
> through other means and it works fine. Any help is much appreciated.

Your code looks fine. The first thing I'd do is to double check you've got the access key / secret access key round the right way, and that they are correct.

Best

Ben

[creztoe]

I used the same access and secret key with S3 Browser and it works
just fine. I am really frustrated with this.

I also use the same keys to access my Amazon SimpleDB using a wrapper
someone wrote for the iPhone and it also works.

[Alex Reynolds]

Amazon's JavaScript S3 signature tester is a good way to locally compare the NSData going into the signature ("StringToSign") and the data that comes out, with what your methods are generating.

-Alex

[Alex Reynolds]

I should probably post a link to that:

http://developer.amazonwebservices.com/connect/entry.jspa?externalID=199

-Alex

[Ben Copsey]

> I used the same access and secret key with S3 Browser and it works
> just fine. I am really frustrated with this.
>
> I also use the same keys to access my Amazon SimpleDB using a wrapper
> someone wrote for the iPhone and it also works.

I tested with your code yesterday using my own S3 account, and it worked perfectly.

If you downloaded ASIHTTPRequest a while ago, you might have been unlucky enough to get a version where S3 support was broken. I think that's probably quite unlikely, but it might be worth updating your copy just in case.

[Robert Hawkey]

Just in case anyone else runs into this, I had this same problem and
the problem came down to having capital letters in my bucket name. I
created my bucked on the AWS Management console, something like:
MyBucket. But, somewhere along the line the process was turning the
MyBucket into mybucket, and I only discovered this by checking the
reply XML from the server reporting the invalid signature and I could
see a line with mybucket in lowercase. Figuring that can't be good I
made a new bucket "mybucket" no caps, and moved all the files into
it. Once I did that the same code worked perfectly.

Rob Hawkey

On May 1, 1:40 am, Ben Copsey <b...@allseeing-i.com> wrote:
> > I used the same access and secret key withS3Browser and it works

> > just fine.  I am really frustrated with this.
>
> > I also use the same keys to access my Amazon SimpleDB using a wrapper
> > someone wrote for the iPhone and it also works.
>

> I tested with your code yesterday using my ownS3account, and it worked perfectly.
>
> If you downloaded ASIHTTPRequest a while ago, you might have been unlucky enough to get a version whereS3support was broken. I think that's probably quite unlikely, but it might be worth updating your copy just in case.

[Ben Copsey]

Hi Robert

> Just in case anyone else runs into this, I had this same problem and
> the problem came down to having capital letters in my bucket name. I
> created my bucked on the AWS Management console, something like:
> MyBucket. But, somewhere along the line the process was turning the
> MyBucket into mybucket, and I only discovered this by checking the
> reply XML from the server reporting the invalid signature and I could
> see a line with mybucket in lowercase. Figuring that can't be good I
> made a new bucket "mybucket" no caps, and moved all the files into
> it. Once I did that the same code worked perfectly.

I think this is because ASIS3Request refers to the bucket using the virtual host style, eg: http://mybucket.s3.amazonaws.com.

IIRC you can perform requests with the REST API in a different way that would allow you to use a mix of upper and lowercase characters, but I think the value of being able to use a subdomain to refer to your bucket probably outweighs the advantage of this, especially if you are making your resources public.

Incidentally, there are other restrictions on the names you can use with the dns style (eg: no underscores), see:

http://docs.amazonwebservices.com/AmazonS3/latest/dev/index.html?BucketRestrictions.html

I should probably add a note on this to the documentation.

Best

Ben