Adjust PutObject satellite endpoint (object retention)

[amwolff]

Goal

This issue is to make meaningful progress on Object Lock implementation within core and edge services. Specifically, to support immutable backups in backup software products like Veeam.

What needs to be done? • Acceptance Criteria

Modify the corresponding to PutObject endpoint on the satellite (the endpoint might be named differently) to respect the lock information passed with the upload request:

• Don't allow locked object versions to be overwritten
• Take into account lock mode and retain-until-date parameters passed by the client
• Legal Hold and governance mode (retention mode) is out of scope at this moment

Summary

Implementation reference.

Note

The Content-MD5 header is required for any request to upload an object with a retention period configured using Amazon S3 Object Lock.

Should only the gateway enforce this?

Depends on…

• Decide where and make it possible to store per-object metadata for Object Lock #400

Links

• https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html
• an easy-to-read and insightful introduction to Object Lock: Using S3 Object Lock