S3 Object Lock FAQ
Below are some of the Frequently Asked Questions (FAQs) pertaining to S3 Object Lock for Wasabi. Additional information on how object lock works and integrates with applications like Veeam Backup & Replication are available in the Wasabi Knowledge Base.
1. How much does it cost to use S3 Object Lock with Wasabi?
There is no additional charge for using S3 Object Lock with Wasabi.
2. Can existing buckets be enabled for S3 Object Lock?
No. To use Object Lock it must be enabled at the time a bucket is created. Buckets using Object Lock must also have Versioning enabled. This is the same process required when using AWS S3.
3. Can the lock (aka retention) of an object be extended or shortened when using Object Lock in Compliance mode?
An object lock can be extended but not shortened. This requires the proper access permissions to the bucket/object and can be executed through your compatible, authorized application or directly through the API.
Locks can NOT be shortened in Compliance mode. Using Object Lock with Compliance mode prohibits everyone from deleting objects until the retention period has expired. Be careful how you use this great power – it comes with great responsibility.
4. What happens if I don’t pay my bill (PayGo) and I used Object Lock with Compliance mode to set a retention period years into the future?
Please refer to the Wasabi Customer Agreement with the stated policies regarding payment and account deletion. Long story short, if you don’t pay your bill, your account can be closed and your data can be deleted. Let’s try not to go there.
Additional information on how to use S3 Object Lock is available in the Wasabi Knowledge Base.