Comments on: Erlang and Amazon’s S3 Storage Service

By: Andrew

Andrew — Mon, 04 Feb 2008 23:53:04 +0000

md: S3 has a single namespace for buckets. I suspect someone has already claimed “KS-test-bucket”. If you try again with a different (and unique) bucket name, it should work. I’ll look at improving the test code to check for this eventuality.

By: md

md — Sat, 02 Feb 2008 14:23:17 +0000

I tried your s3erl library, but running s3test:run/3 errors on creating bucket - message says it’s wrong credentials like this:

=ERROR REPORT==== 2-Feb-2008::15:18:38 ===
** Generic server s3 terminating
** Last message in was {put,”KS-test-bucket”}
** When Server state == {aws_ident,”XXXX”, “XXXX”}
* Reason for termination ==
** {bad_return_value,{s3error,”SignatureDoesNotMatch”,
“The request signature we calculated does not match the signature you provided. Check your key and signing method.”}}
** exception exit: {bad_return_value,
{s3error,”SignatureDoesNotMatch”,
“The request signature we calculated does not match the signature you provided. Check your key and signing method.”}}

Since the list_buckets were ok, it’s not the problem of credentials. Do you think that maybe there is some error in your function for making the Authorization header? Is it possible, that the error does not occur on your system because you don’t have any special characters in credentials? Or maybe missing urlencode somewhere….

By: dda

dda — Sun, 30 Dec 2007 02:40:59 +0000

The pleasures of living away from GMT…

By: Andrew

Andrew — Sat, 29 Dec 2007 18:45:57 +0000

I’ve fixed the problem in the new version of s3erl; thanks for the feedback.

http://nobugs.org/developer/s3erl/s3erl-0.2.tar.gz

By: dda

dda — Sat, 29 Dec 2007 05:38:58 +0000

Tried it and I got this error:

1> s3test:run( “XXXXXXXXXXXXX”, “YYYYYYYYYYYYYYY”, “test.sungnyemun.com”).
Exercising s3erl on bucket “test.sungnyemun.com”

=ERROR REPORT==== 29-Dec-2007::13:36:07 ===
** Generic server s3 terminating
** Last message in was {listbuckets}
** When Server state == {aws_credentials,”XXXXXXXXXXXXX”,
“YYYYYYYYYYYYYYY”}
** Reason for termination ==
** {bad_return_value,{s3error,”RequestTimeTooSkewed”,
“The difference between the request time and the current time is too large.”}}
** exception exit: {bad_return_value,{s3error,”RequestTimeTooSkewed”,
“The difference between the request time and the current time is too large.”}}
2>

Could it be that the time values are based on US time? I am in HK, GMT+8, so this could be a problem…?