Compliance Overview

The compliance feature prevents the deletion of any objects and provides additional information to prove that the original data is not modified since the time it was stored. The compliance feature may be required for certain regulatory needs, but it is also useful to prevent accidental deletion. You can lock compliance mode on to prevent disabling it. However, once it is locked on, compliance mode cannot be unlocked without the intervention of Wasabi Customer Support. This restriction is for your data protection as part of Wasabi’s immutable bucket feature.

Use the compliance feature cautiously. Inappropriate use of this feature will restrict your ability to delete storage buckets and associated files, which will result in storage charges for these objects.

In summary:

• The Compliance feature is used to achieve bucket immutability, and prevents any change or deletion of objects (all objects) in a bucket, until a specified retention time passes.
• Compliance is a bucket-level setting. It takes effect across an ENTIRE bucket, across ALL the objects in that bucket.
• Compliance works with versioning enabled or disabled. If versioning is disabled and you try to upload the same object again before the retention time elapses, you will get an Access Denied error through the Console.
• Compliance can be enabled at any time, even after the bucket has been created.
• When working with a third-party application, there is no third-party application dependency. The Compliance setting is controlled by the Wasabi bucket settings.