This finding is distinct from the other S3 lifecycle findings Parsivex surfaces:
- S3 wrong storage class — the bucket has no lifecycle rules and enough stored data that transitioning to a cheaper storage class (for example Intelligent-Tiering) would save money. It applies to large buckets regardless of versioning status.
- S3 incomplete multipart uploads — abandoned multipart uploads are accumulating because there is no abort rule. The bucket may already have other lifecycle rules.
- Missing lifecycle policy (this page) — the bucket has versioning enabled or suspended but zero lifecycle rules, so noncurrent object versions can accumulate indefinitely with no automatic expiration or tier transition.
A single bucket can appear in more than one of these findings when multiple conditions apply.
What triggers this finding
A versioned or growing S3 bucket with no lifecycle rules configured to manage storage costs.
Typical fix
Add lifecycle rules to expire noncurrent versions, transition objects to cheaper tiers, or clean up incomplete uploads.
Example savings
Varies by bucket size and access patterns — often $5–$100+/month on buckets with versioning enabled.
See also: Severity and savings estimates for how Parsivex calculates figures on your report.