The access to Wasabi's S3 is using the community developed policy (because I think this still isn't officially documented by either Wasabi or Veeam, or if it is it's not linked from the obvious places - HINT! HINT!!). I assume the index upgrade / new v12 approach requires some additional right. Does anyone know what this is, or have a known working policy?
Sorry - I might have had my idiot brain loaded today... I found a couple of permissions missing from the policy. I've updated all the policies to include everything from the list. Strange that this has been working for years for everything except this policy upgrade.
I've submitted suggestion to the docs team to just supply the sample policy, because stating the permissions alone won't enable you to work out how to set up the policy so it works and uses least privilege... I know this was quite a discussion point when Wasabi implemented immutability.
I've just triggered an offload with the new policy in place and it's still failing though - so perhaps those missing permissions weren't the cause.
Correct, it does not seem like a permission issue - we verified the given policy and everything looked OK. We had an idea of what might be the root cause and shared it with the support engineer. He might get in contact with you soon. Thanks!
Turned out this was caused by an intermittent Wasabi cloud issue that resolved itself during the last support call. So, this had nothing to deal with V12 in the end. Thanks!
FYI - I've had the docs of these permissions expanded (a lot!) to include policy templates for most common scenarios, so this is now formally documented rather than being hidden in the forums.