reasoning behind Requirement for s3:ListAllMyBuckets
Hi everyone,
We are currently driving a proof of concept with Wasabi to offload our clients offsite backups. The only thing that currently prevents us from moving forward is the requirement for the ACL to allow s3:ListAllMyBuckets, which would allow customers to list buckets for everyone in our Wasabi "tenant".
I know there is a partner API to work around this and create segregated accounts, but we are not certain the setup and development fees would be worth it for us right now. A majority of our customers cannot save data in the US, so that limit the potential customer base for our Wasabi deployment for the immediate future.
Anyone knows if Veeam plans to remove the requirement for s3:ListAllMyBuckets or what is the reasoning behind it?
Thanks,
Posted Sep 15, 2020, 12:46 PM UTC
I dare ping the great u/gostev to this thread!
Not sure why you got downvoted for doing the right thing!
I'm looking into this. At a first sight this looks like a UI-only requirement to make the Browse functionality working, so it should be possible to make it an optional requirement if we allow typing the bucket name and path in manually.
Thanks for looking into this, it's very much appreciated!