Amazon S3 lifecycle retroactive application -

fairly straightforward question. amazon s3 lifecycle rules set applied data retroactively? if so, sort of delay might see before older data begins archived or deleted?

by way of example, let's have bucket 3 years of backed data. if create new lifecycle data archived after 31 days, , deleted after 365 days, new rule applied existing data? how begin enforced?

yes it's retroactive (i.e. things there , match rule).
there may slight delay (i.e. rules have day granularity , run on daily basis), rules take effect immediately. depending on how data have remove/move may take while if have lot of pre-existing data.

source: s3 faq here: http://aws.amazon.com/s3/faqs/

lifecycle policies apply both existing , new s3 objects, ensuring can optimize storage , maximize cost savings current data , new data placed in s3 without time-consuming manual data review , migration.

after object expiration rule added, rule applied objects exist in bucket new objects added bucket. once objects past expiration date, identified , queued removal. not billed storage objects on or after expiration date, though may still able access objects while in queue before removed. standard delete requests, amazon s3 doesn’t charge removing objects using object expiration. can set expiration rules versioning-enabled or versioning-suspended buckets well.