Skip to main content
Rightsizing · Low severity

S3 Bucket Lifecycle Policy Missing

Without a lifecycle rule every object stays in the class it was written to and is billed at that rate forever, however cold it becomes.

Sign inExplore the playground

Free to start. No card. The playground just needs your work email.

AWSprovider
Lowseverity
Savingswhere it shows up
Guidedfix, after a review

AWS

Found, explained, fixed.

Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.

01

Detect

ZopNight checks this automatically across AWS, with read-only access to the account.

02

Explain

Every finding says exactly what to change: Add a lifecycle policy to the S3 bucket. Where the saving can be proven it is priced; where it cannot, the finding says so.

03

Fix

After a guided review, where you confirm the change, ZopNight applies a lifecycle policy, then checks the change took.

Applies to
S3 Buckets on AWS
The fix, by hand
  1. S3 Console → bucket the resource → Management → Create lifecycle rule.
  2. Scope the rule by prefix (e.g. logs/, backups/, tmp/). Bucket-wide rules are risky.
  3. Add transitions matching access pattern: Standard → Standard-IA at 30d → Glacier Instant Retrieval at 90d (cheap, milliseconds) or Glacier Flexible (minutes-to-hours) / Deep Archive (12+h, cheapest) for cold data.
  4. Add expiry if applicable (logs/ deleted after 365d).
  5. Always add AbortIncompleteMultipartUpload after 7d on the bucket. Multipart orphans are silent cost growth.
  6. Save and confirm via S3 Storage Lens after 14d that storage class shifts are happening.

ZopNight does this for you after a guided review.

Category
Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
Where it appears
The Savings tab of Recommendations, with every affected resource listed.
Rule ID
RC-072
Full reference

S3 Bucket Lifecycle Policy Missing

Related checks

S3 Bucket with Public Access EnabledAWSS3 Bucket Not Requiring HTTPSAWSS3 Bucket Access Logging Not EnabledAWSS3 Incomplete Multipart Uploads AccumulatingAWSLarge S3 Bucket with External Access, Consider Requester PaysAWSS3 Glacier Objects, Consider Deep ArchiveAWS

See the oversized resources in your account.

Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.

Start freeExplore the playground

Prefer to talk it through first? Book 20 minutes with the team.

  • $30M+annualised cloud spend under management
  • 550K+resources tracked since launch
  • 20-60%off the bill in the first month
  • SOC 2Type II report, plus ISO 27001

Figures published on zop.dev.

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·