SignatureDoesNotMatch

[eli007s]

following your example to the letter and providing my key, secret, and bucket information i get the following error

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

any ideas?

[anomalizer]

Could you provide the following info:

• The nginx conf (minus the keys ofcourse)
• Your S3 region
• The S3 url that you wish to proxy to
• The request that you made to nginx (HTTP Verb and URL)

[eli007s]

my regions is us-west-1

what do you mean by http verb?

location ~ ^/data/(.*)$ { proxy_pass http://[myBucket].s3.amazonaws.com/[key]/data/$1;

  aws_access_key [myKey];
  aws_secret_key [mySecret];
  s3_bucket [myBucket];  
  proxy_set_header Authorization $s3_auth_token;
  proxy_set_header x-amz-date $aws_date;
}

[anomalizer]

GET, POST, HEAD etc. etc. I meant HTTP method

[eli007s]

Oh I'm accessing it directly thru the URL

Www.domain.com/data/image.jpg

On Saturday, July 18, 2015, Arvind Jayaprakash notifications@github.com wrote:

GET, POST, HEAD etc. etc. I meant HTTP method

— Reply to this email directly or view it on GitHub https://github.com/anomalizer/ngx_aws_auth/issues/17#issuecomment-122622625 .

[eli007s]

its get

GETx-amz-date:Mon, 20 Jul 2015 20:35:44 GMT /photo11_2x5714619687.jpg

[anomalizer]

Please start watching the branch AuthV4. It now has the most basic support for new regions

[anomalizer]

Please try the new code on master. This should take care of your issue

[rahulravindran0108]

same issue here signature does not match

[rikewang]

I get 403 signaturenotmatch too, I use ceph rgw as S3 service, does ngx_aws_auth(V2) work well @anomalizer

[anomalizer]

This plugin has never been tested with ceph rgw as a backend. Support for ceph would be a new feature

[y2kkarthik]

I am facing same error too while using with auth v4 to s3 in us-east-1. Details in https://github.com/anomalizer/ngx_aws_auth/issues/54

Any thoughts @anomalizer ??

Regards, Karthik

[y2kkarthik]

Got that error fixed. But now it says Access Denied. Does the bucket have to be really public to work with this?

Regards, Karthik

[zmqundead]

Try add this to nginx config: proxy_set_header Host $host;

[bugoverfl0w]

I am facing same error too while using with auth v4 to s3 in us-east-1. Details in #54

Any thoughts @anomalizer ??

Regards, Karthik

Hello,

Did you finish this issue?

Does it work with Ceph rwg s3?

Thanks,

[noplanman]

@anomalizer I get this error too sometimes, is there any fix for this?

Also, what happened to the v4 branch? Is this project abandoned?