Retention for the S3 fixed content device
The S3 fixed content device uses the object lock feature to support retention.
Retention in aligned mode
To support retention in aligned mode, the S3 bucket must be object lock enabled, and the fixed content storage area must work in aligned mode in Content Platform Engine.
- When no retention is specified for an object creation, the bucket default retention, if defined, will be applied.
- You must configure matching minimum and maximum retention settings between the S3 bucket and Content Platform Engine.
Retention in unaligned mode
For S3 fixed content storage area in unaligned mode, if the bucket is object lock enabled and has a default retention defined for the bucket, the S3 fixed content device will always set the retention period to 0 for the object to prevent the default vault retention from being applied. For an object lock enabled bucket with default retention set, to work in unaligned mode, the minimum retention must be set to 0. Content Platform Engine validates this setting at the storage area creation time and document creation time.
Extending the retention period
When you extend the retention, the new retention date will also be validated based on the minimum and maximum retention settings of the bucket. S3 enforces the minimum retention settings for the new retention setting.
For Amazon S3, when you extend the retention, the minimum and maximum retention validation uses the retention extending time as the baseline. For example, if the minimum is 3 days and the maximum is 7 days, and at document creation time the retention is set to 5 days. Then on day 4, if you want to extend the retention, you cannot extend the retention to day 6, because at that time using , Amazon S3 validates the minimum retention (3 days) using day 4 as the baseline. From day 4, you can only extend the retention to a value between day 7 (4+3) and day 11 (4+7). The Content Platform Engine validates the extended retention based on the AWS implementation for all S3 fixed content devices, no matter what the vendor implementation is.