When attempting to configure an archive to a Wasabi S3-compatible bucket, the archive fails with the following error:
"Object locking is not supported by selected container."
This issue occurs even if Object Lock and Versioning are enabled on the bucket at creation time.
This issue is caused by a mismatch between the region of the Wasabi bucket and the endpoint specified during cloud account configuration in Rapid Recovery.
When s3.wasabisys.com is used, it defaults to the us-east-1 region. If the bucket is located in a different region (e.g., us-central-1), the archive operation fails because Rapid Recovery attempts to access the bucket in the incorrect region.
💡 Even though the error references object locking, the root cause is the incorrect endpoint, not the object lock configuration.
Verify the region where the Wasabi bucket is hosted and ensure the correct regional endpoint is used when adding the cloud account in Rapid Recovery.
Use the following endpoints based on the bucket's region:
us-east-1 ➤ s3.us-east-1.wasabisys.com
us-central-1 ➤ s3.us-central-1.wasabisys.com
us-west-1 ➤ s3.us-west-1.wasabisys.com
eu-central-1 ➤ s3.eu-central-1.wasabisys.com
🔗 For a complete list of regional endpoints, refer to the Wasabi Service URLs documentation.
For detailed setup instructions and best practices, refer to:
Setting up S3 Object Locking / Immutable Storage for Rapid Recovery Archives (KB 4376845)
