Policy Enforcement
Consider lifecycle policies for an object 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 i.e. create delete markers before the intended behavior of the operation.
Continuously check objects in the background to verify compliance with lifecycle policies.
Listing queries are not required to evaluate rules for objects returned in the listing. Therefore, listing queries return inconsistent results immediately after policy expiration at midnight UTC when compared with the active SCSP operations.
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, deletion represents creating a delete marker when the bucket/domain has versioning enabled. 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 appear out-of-date in some cases but are eventually consistent over time.