S3 Lifecycle expiry date issue

Background

I have been applied Lifecycle on bucket to expire object after 91 days. However, object can be fetched a few more days although objects aged more than 91 days.

 

Reason

S3 object expirations are processed once a day, at an undetermined time starting at the beginning of each day (midnight 12 AM UTC). The process marks any object for deletion whose expiration date has expired. Amazon S3 then queues these ‘marked for deletion’ objects and removes them asynchronously. So there may be an additional time lag between the expiration date and the date at which Amazon S3 removes an object. This time lag will vary based on the region, few regions are the busiest region (us-east-1), where it will take few days additionally to delete the objects. For this reason, it will not be charged for any associated storage for those objects on or after their expiration date.

Summary

Amazon S3 handles object expirations daily, beginning at midnight UTC. Once an object's expiration date is reached, it is marked for deletion, but actual removal happens asynchronously, with potential delays in busier regions like us-east-1. Despite these delays, storage costs cease after the expiration date, regardless of when the object is physically deleted.

Reference

Why There Is a Delay in an Amazon S3 Lifecycle Rule | AWS re:Post (repost.aws)

Managing the lifecycle of objects - Amazon Simple Storage Service