slot 1: While creating new S3 bucket: The request signature we calculated does not match the signature you provided

[RobertPHeller]

Why am I getting this error?

[RobertPHeller]

Here is the output from amcheck and my amanda.conf
sharky5-amanda.zip

[RobertPHeller]

This is a set of configure files that work under Amanda 3.3.3 under CentOS 7
sharky4-amanda-3.3.3-22.el7.zip

[troglodite2]

The issue is in s3.c perform_request(). While the function is called with verb="PUT" libcurl sends a GET request.

Since the method of the call is part of the S3 authorization hashing, the hashes do not match causing the Signature Error.

libcurl's documentation says that a PUT will be done if the CURLOPT_UPLOAD, CURLOPT_READFUNCTION, and CURLOPT_READDATA are all set.

What the documentation does not say is that only one of CURLOPT_HTTPGET, CURLOPT_UPLOAD, CURLOPT_POST, or CURLOPT_NOBODY can be set. In our case, we set CURLOPT_UPLOAD correctly and then set POST and NOBODY (to zero).

This appears to reset the options to "none" which defaults to "GET" causing the GET instead of PUT.

PR #280