CODEWITHSUNDEEP
amazon-web-servicesamazon-s3amazon-ec2s3-lifecycle-policy
ajay makwana
ajay makwana

Reputation: 99

Lifecycle Policy Not Deleting Deleted Object Permanently On AWS S3 bucket

Versioning is not suitable in my case because if the user wants to delete anything in storage it would be deleted permanently not soft-deleted but for the backup purpose, I have to use Cross-Region Replication and to use CRR I need to enable Versioning.

I tried to delete those object which has Delete-marker as the current version and non-current version as a soft deleted object. here is my life cycle rule policy. No Transitions, No current version expiration.

Only applied the Previous version permanently delete so that it considers delete marker as the current version and soft-deleted object as the previous version and delete it permanently BUT I DON'T KNOW IT IS NOT WORKING...!

I checked on next day the deleted version is still there also I have added multiple version of the same object and that versions are also not deleted.

Upvotes: 2

Views: 13157

Answers (1)

Chris Williams
Chris Williams

Reputation: 35258

If you have only just enabled it, it might still be queuing objects that need to be deleted.

Lifecycle policies do not delete exactly after this marker, in fact actions are queued and processed later on.

When an object reaches the end of its lifetime, Amazon S3 queues it for removal and removes it asynchronously. There might be a delay between the expiration date and the date at which Amazon S3 removes an object. You are not charged for storage time associated with an object that has expired.

Sometimes when you first configure it can be slightly delayed (because it has not queued anything) so I would suggest checking back in a couple of days when this process should now have happened.

More information is available in the Understanding object expiration documentation.

Upvotes: 2

Related Questions