| Table of Contents |
|---|
Object locking prevents object versions from being deleted or overwritten – for a fixed amount of time or indefinitely. Use an object lock to help meet regulatory requirements requiring WORM storage, or to simply add another layer of protection against object changes and deletion.
...
While object locking is implemented fully from Gateway 7.6 onwards, in order to use this feature, Swarm Storage 12.0 or above must be running because it relies on the Swarm lifepoints feature to prevent the deletion of locked objects until a certain date has passed.
...
Differences Between S3 and Swarm's Implementation of Object Locking
In S3, a DELETE request would result in a delete marker, shadowing the locked object version. Swarm's implementation deviates from that logic – it rejects any DELETE requests for indelible objects with an HTTP 403 Forbidden error.
When Gateway gets a HTTP 403 Forbidden error from Swarm, it checks if the object is locked. Gateway simulates the S3 behavior creating a new (unlocked) object version, immediately followed by a DELETE, thus creating a delete marker.
For SCSP, use a configuration flag to pick the desired behavior:
...