Build S3 lifecycle configuration rules with guided transitions and expiration settings.
Last verified: April 2026
Output will appear here...The builder constructs a valid S3 lifecycle configuration JSON object by composing rule objects with Filter, Transitions, NoncurrentVersionTransitions, Expiration, and AbortIncompleteMultipartUpload fields. It validates that transition days are in ascending order, enforces AWS minimum-day constraints (30 days for IA, 90 days for Glacier), and ensures no conflicting actions exist in the same rule.
The S3 Lifecycle Rule Builder helps you create and validate Amazon S3 lifecycle configuration rules without hand-editing JSON. It walks you through defining transition actions that automatically move objects between storage classes such as Standard, Intelligent-Tiering, Glacier Instant Retrieval, Glacier Flexible Retrieval, Glacier Deep Archive, and S3 Standard-IA over time. You can also configure expiration rules to automatically delete objects or incomplete multipart uploads after a specified number of days. The generated JSON is ready to paste into the AWS CLI, CloudFormation, or Terraform, saving you from trial-and-error and misconfigured policies.
Always add a rule to clean up incomplete multipart uploads (AbortIncompleteMultipartUpload with DaysAfterInitiation: 7). Failed uploads can silently accumulate gigabytes of hidden storage costs.
Intelligent-Tiering has zero retrieval fees and automatically moves objects between access tiers. For unpredictable access patterns, it's often cheaper than manually managing Standard-IA transitions.
Glacier Deep Archive has a 12-hour minimum retrieval time for Standard retrieval. If you might need faster access, use Glacier Flexible Retrieval (which offers 1-5 minute Expedited retrievals) even though it costs more per GB.
AWS requires objects to remain in S3 Standard for at least 30 days before transitioning to Standard-IA or One Zone-IA. The builder enforces this constraint automatically so your generated rules are always valid.
Yes. A single lifecycle rule can include multiple transition actions (e.g., move to IA at 30 days, then Glacier at 90 days) and an expiration action (e.g., delete at 365 days). The builder lets you stack these actions and validates the ordering.
Yes. You can configure rules that target current versions, noncurrent versions, or expired object delete markers. This is essential for buckets with versioning enabled where old versions accumulate storage costs.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.