Versioned S3 bucket grows much faster than expected
Versioning keeps every version. Without lifecycle, versions and delete markers pile up.
Try this first
- 1Add a lifecycle rule: NoncurrentVersionExpiration after, e.g., 30 days
- 2Also expire delete markers in the same rule
- 3Audit with S3 Storage Lens which prefixes cause the bloat
- 4Consider whether versioning is truly needed, or use Object Lock
When to bring us in
For backup use cases, S3 Object Lock with compliance mode is sturdier than versioning alone.
See also
- Everyone logs in with the AWS root accountRoot is for emergencies and billing. Day-to-day work belongs in IAM users or SSO.
- Every developer has AdministratorAccessAdministratorAccess everywhere is convenient now, painful later. Start with role-based policies.
- Everyone has individual IAM users with their own passwordIdentity Center (formerly AWS SSO) links to your IdP and issues temporary credentials per session.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.