Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 12 additions & 7 deletions pages/object-storage/how-to/manage-lifecycle-rules.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -3,15 +3,16 @@ title: How to manage lifecycle rules from the console
description: Set and manage lifecycle rules for Object Storage.
tags: object storage object-storage lifecycle lifecycle-rule abort incomplete multipart upload expire version
dates:
validation: 2025-10-21
validation: 2026-09-29
posted: 2021-05-27
---
import Requirements from '@macros/iam/requirements.mdx'
import LifecycleMinimalDurationMessage from '@macros/object-storage/lifecycle-minimal-duration-message.mdx'

The Scaleway console allows you to automatically manage the lifecycle of your object by setting lifecycle rules. These rules allow you to automatically:
- Delete your objects and their versions by setting expiration durations
The Scaleway console lets you automate object lifecycle management by setting rules to:
- Delete your objects and their versions by setting an expiration date or duration
- Transition objects and their versions to a colder storage class
- Expire delete markers that have no non-current versions
- Abort incomplete [multipart uploads](/object-storage/how-to/abort-incomplete-mpu/)

You can either apply these rules to each object in a bucket or to a specific set of objects by using filters based on prefixes and tags.
Expand Down Expand Up @@ -54,16 +55,20 @@ Lifecycle rules only allow the following transitions:

7. Configure the behavior of the lifecycle rule:

- Automatically transition the current version of your objects to a colder storage class after the specified number of days.
- Automatically transition the current version of your objects to a colder storage class on a specified date or after a specified number of days.

- Automatically transition the non-current versions of your objects to a colder storage tier after the specified number of days.
- Automatically transition non-current versions of your objects to a colder storage class after the specified number of days once they become non-current. Optionally, you can specify the number of non-current versions to retain.

- Automatically expire and delete the current version of your objects after the specified number of days.
- Automatically expire and delete the current version of your objects on a specified date or after a specified number of days, or expire delete markers that have no non-current versions.

- Automatically expire and delete non-current versions of an object after a specified number of days once it becomes non-current.
- Automatically expire and delete non-current versions of an object after a specified number of days once it becomes non-current. Optionally, you can specify the number of non-current versions to retain.

- Automatically abort [incomplete multipart uploads](/object-storage/api-cli/multipart-uploads/#aborting-a-multipart-upload) after a specified number of days.

<Message type="note">
You can add several transitions for current versions and non-current versions to the same rule.
</Message>

8. Click **Next Step** to proceed.

9. Review the summary of your lifecycle rule, then click **Create lifecycle rule** to confirm.
Expand Down
Loading