---
title: "Why do I receive error message \"the selected object storage does not support S3 Object Lock feature\" in Veeam?"
slug: "why-do-i-receive-error-message-the-selected-object-storage-does-not-support-s3-object-lock-feature-in-veeam"
updated: 2026-04-29T21:06:50Z
published: 2026-04-29T21:06:50Z
canonical: "docs.wasabi.com/why-do-i-receive-error-message-the-selected-object-storage-does-not-support-s3-object-lock-feature-in-veeam"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wasabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why do I receive error message "the selected object storage does not support S3 Object Lock feature" in Veeam?

When setting the Wasabi Veeam Object Lock Integration, you may encounter the error **"the selected object storage does not support S3 Object Lock feature"**when trying to set immutability inside Veeam Backup & Replication. This is an indication that Veeam was unable to validate Object Lock information about your bucket.

Here is a list of things you can do in order to verify your setup is correct on Wasabi:

- Make sure that you have selected a bucket with the Object Lock feature enabled.
- Check that the Object Locking setting looks like the image below. It is not necessary to configure this, since Veeam Backup & Replication will automatically use Compliance object lock mode for each uploaded object.

![mceclip0.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/12451928030875.png)

- Veeam Backup & Replication uses an API call that will return information about the Object Lock setting in your bucket. There are three types of responses:

Check that the sub-user, whose Access and Secret keys you set in Veeam, has permission to retrieve the Object Lock information about the bucket. For information on Veeam’s suggest policy, refer to [How to Create Secure IAM Policy for Connection to S3 Object Storage](https://www.veeam.com/kb3151).
  - 200 - with the Object Lock configuration.
  - 404 - Object Lock configuration not found => Bucket isn't an Object Lock bucket.
  - 403 - Access denied => this will get translated into Veeam as Bucket with no Object Lock.