The problem
Cloud Storage buckets often start small and then grow quietly as exports, backups, build artifacts, and logs pile up. Without lifecycle management, stale data remains in the hot storage class forever.
Why it happens
- Buckets are created quickly for a project need, but lifecycle management is not included in the initial Terraform or console setup.
- Teams assume storage growth will be reviewed later, but no ownership process exists.
- Log and export buckets are treated as operational plumbing rather than billable resources.
What this means for cost
Estimated monthly
$50 to $1,400/mo
Estimated annual
$600 to $16,800/yr
This waste pattern often shows up as $50 to $1,400/mo in recurring monthly cost, or roughly $600 to $16,800/yr if it sits untouched for a year.
How to detect missing GCS lifecycle policies
The key signal is a bucket with no lifecycle block at all, or a lifecycle block that exists but contains zero rules, especially when it stores logs, exports, artifacts, or other time-bounded data.
Inspect bucket lifecycle configuration:
gcloud storage buckets describe gs://my-bucket --format=jsonLook for the lifecycle block. If it is missing or the rule list is empty, then object retention is still entirely manual.
Buckets worth checking first include application logs, exports, temporary staging areas, and CI artifact buckets. These are common sources of gradual but persistent storage growth.
What this detector actually checks
This detector stays deliberately simple:
- missing lifecycle block: finding
- lifecycle block with zero rules: finding
- any non-empty lifecycle rule set: aligned
That simplicity keeps the signal clear, but it also means this page is not a full policy-quality review. A bucket can avoid a finding here and still have a lifecycle policy that is too conservative for its actual data pattern.
How to fix missing GCS lifecycle policies
Define lifecycle rules that match the bucket purpose. For example, temporary exports may expire after 30 days, while audit archives may transition to colder storage first.
resource "google_storage_bucket" "artifacts" {
name = "my-artifacts-bucket"
location = "US"
lifecycle_rule {
condition {
age = 30
}
action {
type = "Delete"
}
}
}If the bucket contains mixed data types, segment it by purpose before applying a uniform retention rule.
Caveats and overlap boundaries
Some buckets intentionally retain data indefinitely for compliance, audit, or archive use cases. This detector also does not attempt to evaluate whether an existing lifecycle rule is aggressive enough. It answers a narrower question: is retention still completely manual?
Versioning-specific archived-generation cleanup is a nearby but narrower problem. This detector covers buckets with no lifecycle rules at all, not whether a versioned bucket has the right archived-object cleanup policy.
How Cloud Waste Hunter helps
Cloud Waste Hunter finds buckets with missing lifecycle management, calls out storage patterns drifting without explicit retention controls, and gives operators a clean first pass for storage-retention hygiene. For adjacent storage policy work, review the GCP Storage Cost Optimization guide.
FAQ
Should every bucket have a lifecycle policy?
Not every bucket needs aggressive deletion, but most operational buckets benefit from explicit retention rules so storage growth matches business intent instead of defaulting to forever.
Does an empty lifecycle block count as aligned?
No. The detector treats a missing lifecycle block and a lifecycle block with zero rules the same way because both leave retention fully manual.
Is a transition-only lifecycle rule enough for this detector?
Yes in v1. Any non-empty lifecycle rule set suppresses the finding, even though a conservative or transition-only rule may still leave savings on the table.