Skip to content

doc(obj): add note on transition rules minimal duration #6215

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
SamyOubouaziz merged 3 commits into from
Feb 23, 2026
Merged

doc(obj): add note on transition rules minimal duration #6215

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3bc8f8f
doc(obj): add note on transition rules minimal duration
SamyOubouaziz Feb 20, 2026
9b3b361
doc(obj): update
SamyOubouaziz Feb 23, 2026
c10af74
doc(obj): update
SamyOubouaziz Feb 23, 2026
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
18 changes: 12 additions & 6 deletions pages/object-storage/api-cli/lifecycle-rules-api.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,17 +17,16 @@ import Requirements from '@macros/iam/requirements.mdx'
You can configure the lifecycle of a group of objects so that their storage costs can be effectively managed. A lifecycle configuration is a set of rules that defines actions applied to a group of objects stored on Object Storage.

Currently, the **expiration**, **transition**, and **incomplete multipart uploads** actions are supported on the platform:
* **Expiration** defines when objects expire. This allows for the automatic deletion of objects on your behalf.
* **Expiration** defines when objects expire. Expired objects are automatically deleted.
* **Transition** defines when objects change storage classes.
* **Incomplete Multipart Uploads** allows you to stop uploads automatically if they are not completed.

<Message type="important">
Lifecycle rules only allow the following transitions:
- Standard Multi-AZ -> Standard One Zone
- Standard Multi-AZ -> Glacier
- Standard One Zone -> Glacier
- Transition rules created or updated after February 19, 2026 must observe the following minimal durations before applying:
- Objects must be stored for at least 30 days before transitioning to Standard One Zone.
- Objects must be stored for at least 90 days before transitioning to Glacier.

Refer to our [dedicated documentation](/object-storage/how-to/edit-storage-class/) to manually change the storage class of your objects.
These minimal duration do not apply to lifecycle rules created before February 19, 2026 unless they are updated. The duration requirements above will then apply.
</Message>

There might, for example, be a need to store log files for a week or a month, after which they become obsolete. It is possible to set a lifecycle rule to delete them automatically when they become obsolete. If you consider that a 3-month-old object is rarely used but still has a value, you might want to configure a rule to send it automatically to [Scaleway Glacier](/object-storage/faq/#what-is-the-cold-storage-glacier-class), for example.
Expand Down Expand Up @@ -133,6 +132,13 @@ This applies the `Prefix` rule *and* the `Tag`.
**Parent**
: `Rule`

<Message type="note">
Lifecycle rules only allow the following transitions:
- Standard Multi-AZ -> Standard One Zone
- Standard Multi-AZ -> Glacier
- Standard One Zone -> Glacier
</Message>

### Day

**Description**
Expand Down
Loading