| Table of Contents | ||||
|---|---|---|---|---|
|
Policy Enforcement
Lifecycle policies for an object are considered during SCSP operations. The expiration policies are evaluated to verify the object is “live” before proceeding with the SCSP operation.
In a versioning-enabled bucket, SCSP operations on objects apply an expiration rule to trigger an action that the delete markers are created before the intended behavior of the operation.
Objects are continuously checked in the background to verify compliance with lifecycle policies.
Listing queries are not required to evaluate rules for objects returned in the listing. Therefore, they may return inconsistent results while comparing when compared with the active SCSP operations, especially soon after a policy expiration.
Listing queries provide an eventual consistency subject for background policy evaluation.
Policy Action
The action is the deletion of an object or object version. In the scenario of a current object deletion, while the bucket or domain has versioning enabled, deletion means creating a delete marker. The delete marker contains a timestamp consistent with the lifecycle policy expiration time, perhaps the creation of the delete marker occurred.
A liveness check is performed on the object as part of SCSP requests for Lifepoint headers (policies).
The policies are set up to “fire” at midnight UTC; this requires components and processes provided by gateway installation. Listing requests for expired objects may appear out-of-date in some cases but they are eventually consistent. If required, customers can disable the Cron job.