Search found 5 matches

by divv
Mon May 04, 2020 1:56 am
Forum: Cloud Storage Related Topics
Topic: Support for AWS Signature Version 4.
Replies: 12
Views: 23356

Re: Support for AWS Signature Version 4.

hi Tobias, Many thanks for the new version, unfortunately we did not find any success with it. Is there anything I can send you that might help to replicate the setup? I could probably provide a sanitised CloudFormation template? And is there a way to export and send you the Syncovery profile? Regar...
by divv
Fri May 01, 2020 5:39 am
Forum: Cloud Storage Related Topics
Topic: Support for AWS Signature Version 4.
Replies: 12
Views: 23356

Re: Support for AWS Signature Version 4.

Hello,

Yes, updating the ini file worked, although it does make it challenging to deal with multiple S3 buckets. For now it looks like we could get away with it as only one S3 destination requires Server Side Encryption.

A fix would be appreciated, but perhaps non-urgent.
by divv
Thu Apr 30, 2020 10:44 pm
Forum: Cloud Storage Related Topics
Topic: Support for AWS Signature Version 4.
Replies: 12
Views: 23356

Re: Support for AWS Signature Version 4.

Hi Tobias,

That makes sense! Especially if you have an enormous amount of files...
We'll try modifying the .ini file.

Thanks for your help.
by divv
Thu Apr 30, 2020 9:43 am
Forum: Cloud Storage Related Topics
Topic: Support for AWS Signature Version 4.
Replies: 12
Views: 23356

Re: Support for AWS Signature Version 4.

We are using v8.19, but I've also tested with v8.67a (latest) and 9.00rc2. Interesting that we are getting this behaviour. The S3 bucket is configured to use default encryption using a customer managed key. We have a bucket policy that blocks AES256, and also only allows one kms-key-id to be used. I...
by divv
Thu Apr 30, 2020 6:53 am
Forum: Cloud Storage Related Topics
Topic: Support for AWS Signature Version 4.
Replies: 12
Views: 23356

Support for AWS Signature Version 4.

Hello, When trying to upload to an S3 bucket with AWS KMS default encryption enabled (AES256 is expressly forbidden by policy), we receive the following error (formatting mine and info redacted): (Bad Request <?xml version="1.0" encoding="UTF-8"?> <Error> <Code>InvalidArgument</Code> <Message>Reques...