Created Lifecycle policy for deleting objects but didn't delete

Hello,

I checked the screenshot and the Lifecycle rule configuration. I can see you have set it up to expire the current version of the objects after 130 days of it's creation on prefix "frames/1/" . Since the S3 bucket name is not given could you please check if the versioning is enabled or not. If the versioning is enabled please apply the lifecycle rule on the non-current versions of the objects as well.

Moving ahead if the versioning is not enabled the Lifecycle rule seems to be correct. As you have mentioned that you have 10M of objects please note that depending upon the number of objects, actual time of expiration and expiry date set by life cycle rule may differ. However, please be assured that once the rule sets the expiry date you will not be charged for those object storage.

Please note that there might be a delay between when the lifecycle rule is satisfied and when the action for the rule is complete. Changes in billing are applied when the lifecycle rule is satisfied, even if the action hasn't been completed. Examples of this include: - If you have a lifecycle rule for object expiration, then you won't be charged for storage after the object expiration time, even if the object isn't expired immediately.

So, Kindly wait for few more days and please be assured that lifecycle will asynchronously delete the objects and you will not be charged for the objects marked for expiry. Meanwhile in order to check if the Lifecycle rule has been applied or not you can perform head-object API.

aws s3api head-object --bucket bucket-name --key frames/1/objectname