On Wed, Jun 8, 2016 at 4:29 AM <[email protected]> wrote: > > > Am Mittwoch, 8. Juni 2016 09:32:37 UTC+2 schrieb [email protected]: >> >> >> >> Am Dienstag, 7. Juni 2016 20:42:05 UTC+2 schrieb Daniel Farina: >>> >>> >>> What version of WAL-E and boto? Newer versions of wal-e all use SigV4 >>> and that has been working well and confirmed working in eu-central-1. >>> >>> >> >> Dear Daniel >> >> Thank you very much for your reply. I am using WAL-E version 0.9.2 and >> boto version 2.39.0. I am also using an S3 compatible storage rather than >> Amazon S3, though the configuration is the same and I can access the >> storage with my credentials through other means (e.g S3 Browser, >> duplicity), just not with WAL-E. >> > > Something else I found: The storage we have uses the signature algorithm > HMAC-SHA1 V2, whereas SigV4 uses HMAC-SHA256 as far as I understand, which > would explain the error. Can you confirm this and if so, what would be the > best workaround? >
So you are using WALE_S3_ENDPOINT? I'm reasonably sure that I turned off Sigv4 when this was in use, attempting to avoid this outcome, so the problem could be something else. Perhaps confirm that WAL-E is attempting to use SigV4? You may have to enable debug output in boto to see what's going on, or instrument the code. What S3-compatible software are you using? I don't know much about any of them in particular, but I'd like to know to get a sense of what people are doing with WAL-E. -- 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.
