S3-compatible Object Lock Beta Now Available!

Dear Storj Community,

We’re excited to announce the beta release of S3-compatible Object Lock! Object Lock is a feature that allows data stored in an S3-compatible bucket to be made immutable, preventing any modifications or deletions for a specified retention period. This beta currently includes Compliance Mode.

How to Participate:

  • If you are already part of the Object Versioning beta:
    • You now have automatic access to Object Lock. Simply navigate to your versioning-enabled project and start using Object Lock today.
  • If you want to join the beta:

Learn more:

Check out the full documentation here: Object Lock Documentation

What’s Next:

We’re working on adding Governance Mode, Legal Hold, and the PutObjectLockConfiguration action to deliver a fully feature-complete S3-compatible Object Lock solution.

5 Likes

Some additional links:

2 Likes

After the emotional rollercoaster of all the TTL data: I’m 100% in-favor of any new features that keep files around longer! :heart_eyes:

5 Likes

When I was looking earlier at some of the commits I was wondering, how is this implemented in presence of TTL data? Does TTL expiration override compliance mode?

We’ve made them mutually exclusive, you get an error if you try to lock an object with ttl set and vice versa.

2 Likes

You may set one version in Lock, and upload another one with TTL. When TTL would expire, this version would be removed, the locked one will remain.
But you wouldn’t be able to lock the TTL version.

1 Like