You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Transition rules created or updated after February 10, 2026 in the Warsaw region, and after February 18, 2026 in the Paris region, must observe the following minimal durations before applying:
7
+
- Objects must be stored for at least 30 days before transitioning to Standard One Zone.
8
+
- Objects must be stored for at least 90 days before transitioning to Glacier.
9
+
10
+
These minimal durations do not apply to lifecycle rules created before these dates, unless they are updated. The duration requirements above will then apply. They also do not apply to the Amsterdam region.
@@ -21,13 +22,7 @@ Currently, the **expiration**, **transition**, and **incomplete multipart upload
21
22
***Transition** defines when objects change storage classes.
22
23
***Incomplete Multipart Uploads** allows you to stop uploads automatically if they are not completed.
23
24
24
-
<Messagetype="important">
25
-
- Transition rules created or updated after February 10, 2026 in the Warsaw region, and after February 18, 2026 in the Paris region, must observe the following minimal durations before applying:
26
-
- Objects must be stored for at least 30 days before transitioning to Standard One Zone.
27
-
- Objects must be stored for at least 90 days before transitioning to Glacier.
28
-
29
-
These minimal durations do not apply to lifecycle rules created before these dates, unless they are updated. The duration requirements above will then apply. They also do not apply to the Amsterdam region.
30
-
</Message>
25
+
<LifecycleMinimalDurationMessage />
31
26
32
27
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.
33
28
@@ -55,10 +50,6 @@ Each `Rule` consists of the following:
55
50
-`Status` whether the rule is in effect (a rule can be present but `Disabled`)
56
51
- Lifecycle transition(s) to perform on the selected objects
57
52
58
-
<Messagetype="important">
59
-
Lifecycle rules are limited to 500,000 jobs per day. Beyond this limit, you can [transition](/object-storage/how-to/edit-storage-class/) or [delete](/object-storage/how-to/delete-an-object/) your objects manually.
With the Scaleway console, you can use lifecycle rules to [manually](/object-storage/how-to/edit-storage-class/) or automatically change the storage class of your objects. These rules also allow users to set expiration dates for objects and their versions.
13
13
14
14
Lifecycle rules also allow you to automatically abort incomplete [multipart uploads](/object-storage/api-cli/multipart-uploads/).
15
15
16
+
<LifecycleMinimalDurationMessage />
17
+
16
18
<Requirements />
17
19
18
20
- A Scaleway account logged into the [console](https://console.scaleway.com)
@@ -40,8 +42,6 @@ Lifecycle rules also allow you to automatically abort incomplete [multipart uplo
40
42
9. Review the summary of your lifecycle rule, then click **Create lifecycle rule** to confirm.
41
43
42
44
<Messagetype="important">
43
-
- Lifecycle rules are limited to 500,000 jobs per day. Beyond this limit, you can [transition](/object-storage/how-to/edit-storage-class/) or [delete](/object-storage/how-to/delete-an-object/) your objects manually.
44
-
45
45
- Lifecycle rules only allow the following transitions:
0 commit comments