Configure Wasabi on Cloud Connect

Is Direct Connection any different than adding a repository to your VCC server?  The help explains what can be used and Wasabi is one of them - Backup to Object Storage - Veeam Cloud Connect Guide

Hey

you have this fabulous guide of Luca Dell’Oca: https://fromthearchitect.com/wp-content/uploads/2022/09/VBR12-and-Secure-Mode.pdf

I used this one to implement DC in my architecture.

I have read, it’s very detailed about theory, but I search a guide for configuration or someone have already configured.

From what I gather all you do is add Wasabi as a repository and then you can point your Tenants to that repository in their configuration settings.

I did with this guide.

On wasabi side create a bucket with your configuration immutable or not

After you have to create a user to access to this bucket and assign two policies 
see : https://www.veeam.com/kb3151
For the second policy I had to remove the line : "iam:TagUser" to be valided on the Wasabi Side.

Next just configure this new bucket as repository on your Veeam Cloud Connect server.
And enable the STS/IAM

After you just have to assign this repository to your tenant 
 

 I have already used the Luca Dell’O’s guide. it worked

Hi All,

I have terminated now my test on Wasabi Direct Connected and configured on VCC side.
Only one things about policy on Wasabi side: work only if have “WasabiFullAccess” policy added to other policy from KB3151.
Finded same issue in forum solved with same workaround: https://forums.veeam.com/object-storage-as-backup-target-f52/changes-for-iam-rules-in-v12-1-needed-t91353.html