Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with buckets in US Standard region #18

Closed
antranapp opened this issue Nov 27, 2012 · 7 comments
Closed

Problem with buckets in US Standard region #18

antranapp opened this issue Nov 27, 2012 · 7 comments
Labels
bug This issue is a bug.

Comments

@antranapp
Copy link

I created a bucket in US Standard region. Initialize the s3client using Region::US_EAST_1 . When trying to upload a file, i received this error "The request signature we calculated does not match the signature you provided. Check your key and signing method."

Change Region to Region::US_WEST_1, i received this error: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.

Now i created a bucket in Ireland region and intialize s3Client using Region::EU_WEST_1, everything works fine.

i created a bucket in North California region and intialize s3Client using Region::US_WEST_1, everything works fine.

i created a bucket in Oregon region and intialize s3Client using Region::US_WEST_2, everything works fine.

So basically, i have problem with bucket created in US Standard region

@jeremeamia
Copy link
Contributor

This problem may already be addressed. Please test again with the master branch of the SDK. If the problem still persists, we'll definitely take a look.

@jeremeamia
Copy link
Contributor

Just saw that this was posted on the forums as well: https://forums.aws.amazon.com/thread.jspa?threadID=110788&tstart=0.

Let me know if this is an issue after using the master branch. Thanks.

@antranapp
Copy link
Author

it is solved using master branch. Thanks

@jeremeamia
Copy link
Contributor

Thanks for verifying. I'm glad it works. We should be tagging a release soon so you don't have to pull off of master.

@xmarcos
Copy link

xmarcos commented Sep 9, 2013

Any chance this could be related to this issue? https://forums.aws.amazon.com/thread.jspa?threadID=134543.

@jeremeamia
Copy link
Contributor

@xmarcos That forum issue definitely looks like clock skew, but we'll look into it more before posting back on the forum.

@xmarcos
Copy link

xmarcos commented Sep 9, 2013

@jeremeamia thanks, i didn't want to open an issue because it seems to be a server side problem.

FYI: there is a consistent 5 minute and 20 second difference between the time on the server and the expected one on the Amazon endpoint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug.
Projects
None yet
Development

No branches or pull requests

3 participants