- 新しい順
- 投票が多い順
- コメントが多い順
The triggering of lifecycle rules is an automated process that is triggered at 12 am UTC[1] and we list the objects in your bucket and find the objects eligible for storage class transition or expiration (deletion). Then, the actions are applied on the objects asynchronously[2]. Depending on the number of objects, it could take a few days for the actions to complete, especially if there are millions of objects eligible for changes.
You can refer to this article to troubleshoot why isn't the lifecycle rule on your Amazon S3 bucket working even though you applied it more than one day ago [3].
Hope this helps,
Jon
[2] https://docs.aws.amazon.com/AmazonS3/latest/dev/lifecycle-expire-general-considerations.html
[3] https://repost.aws/knowledge-center/s3-lifecycle-rule-delay
Typically transition rules triggers once every day from backend and in dashboard it takes bit of time to show as well (depends on number of objects getting transitioned). Possible for you to share the lifecycle policy here , possibilities of some missing step in lifecycle settings.
My bucket has 2 folders/prefix: stage and archive.
Requirement: all files older than 1 day located in the "stage" folder must be moved to glacier area. the others must remain in the standard area.
Is the file size important? Because some my files are 0kb and They have not been migrated
Could you please help me to understand?