Object Lifecycle Management in Google Cloud Storage applies rules at the bucket level: each rule pairs one or more conditions (such as object age in days, storage class, or number of newer versions present) with an action, either transitioning the object to a cheaper storage class or deleting it outright.
Lifecycle Rules
- Common conditions include age (days since creation), createdBefore a date, and matchesStorageClass, and can be combined so a rule only fires when all conditions are met
- Actions include SetStorageClass (for example, move Standard objects to Nearline after 30 days, then Coldline after 90, then Archive after 365) or Delete
- Rules are evaluated roughly once a day, not instantly the moment an object crosses a threshold, so a transition can lag by up to 24 hours
Workflow fit: pair predictable access patterns (logs, backups, media that cools off after launch) with a lifecycle rule so storage costs step down automatically instead of requiring a manual cleanup job.
Use cases
Intro: Use cases for automation
- Move old logs to cheaper storage in Google Cloud Storage
- Expire temporary data after project completion
- Archive backups to nearline storage via lifecycle rules
- Regenerate indexes before data retention windows end
- Compliance-oriented purges on data age
- Tiered storage approach for cost optimization
- Automate retention reports for governance
Closing note: Lifecycle automation scales with Google Cloud Storage.