diff options
| -rw-r--r-- | doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_3_8d4217b54a37eabfd12016c04c7e55b1._comment | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_3_8d4217b54a37eabfd12016c04c7e55b1._comment b/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_3_8d4217b54a37eabfd12016c04c7e55b1._comment new file mode 100644 index 000000000..a53456b8d --- /dev/null +++ b/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_3_8d4217b54a37eabfd12016c04c7e55b1._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2015-02-09T18:30:46Z" + content=""" +Well, looks like git-annex is using the IAM credentials you're providing. + +You could try to use a different S3 client on +the same bucket to check if the credentials are good. + +This may be a problem with the credentials not allowing some actions, +like creating a bucket. Which is the action git-annex is failing at. + +The bucket does already exist, right? Does it contain an "annex-uuid" +file? Does that file contain "a7e22956-5ce2-11e2-97a5-6f33220ffbf3"? +"""]] |