Dear Daniel Finally have found the error and no it's not the signature algorithm. The WALE_S3_PREFIX in my example was simply wrong, I had the address of the endpoint in it as well. Now this alone should not have given the signature error, but a simple "NoSuchBucket" as I found out reconstructing the error. Problem was I also had a typo in that address, an upper case letter instead of a lower case one. The reason I didn't see that is because the variable WALE_S3_ENDPOINT doesn't seem to care about the lower case letter. Same is true for duplicity, another backup tool, which I am using. Altogether it obscured the actual error. I am still not entirely sure why I got the SignatureDoesNotMatch error, perhaps you would like to investigate that?
In any case, thank you for effort to help. -- You received this message because you are subscribed to the Google Groups "wal-e" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
