Date update & duplication

Author: Y0Coss

pages/storage_and_backup/object_storage/s3_bucket_lifecycle/guide.de-de.md

@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Smart Storage Management with Lifecycle Rules
 excerpt: Learn how to optimise your storage costs with OVHcloud lifecycle rules
-updated: 2025-05-13
+updated: 2025-06-05
 ---
 
 <style>
@@ -54,14 +54,7 @@ When an object reaches the end of its lifetime based on its lifecycle configurat
 - **versioned**: a delete marker is created and becomes the current version. You can also choose how many old versions you want to keep. If the current object version is the only object version and it is also a delete marker, that delete marker will be removed.
 - **versioning-suspended**: we currently do not allow for the suspension of versioning if you have a lifecycle configuration in effect and vice-versa. We currently do not allow for the upload of a lifecycle configuration if versioning is suspended on the bucket.
 
-> [!warning]
-> 
-> The release of the feature will be done in 2 phases:
->
-> - Phase 1: support for expiration only
-> - Phase 2: support for transitions
-
-## Expiration (available)
+## Expiration
 
 Lifecycle rules are processed asynchronously and on a best-effort basis. Most rules are applied within 24 hours, but for very large buckets or when processing many objects, it might take longer. During this delay, you continue to be billed for the object's current storage tier, even if the rule (e.g., expiration or transition) has already been triggered but not yet completed. For example, if an object is set to be deleted on day 30 but is only processed on day 32, you may be billed for an additional two days.
 
@@ -393,7 +386,7 @@ In a versioned bucket, the following configuration does the following actions:
 
 ///
 
-## Transition (coming soon)
+## Transition
 
 ### Supported transitions
 
@@ -403,11 +396,12 @@ In a versioned bucket, the following configuration does the following actions:
 
 The following are the currently supported transitions:
 
-| from/to          | High Performance | Standard  | Standard Infrequent Access |Cold Archive |
-| ---------------- | ---------------- | --------- | -------------------------- |------------ |
-| High Performance |        -         | yes       |             yes            | no          |
-| Standard         | forbidden        | -         |             yes            | no          |
-| Cold Archive     | forbidden        | forbidden |             forbidden      | -           |
+| from/to          | High Performance | Standard  | Infrequent Access |Cold Archive |
+| ---------------- | ---------------- | --------- | ----------------- |------------ |
+| High Performance |        -         | yes       |    yes            | no          |
+| Standard         | forbidden        | -         |    yes            | no          |
+| Infrequent Access| forbidden        | forbidden |    -              | no          |
+| Cold Archive     | forbidden        | forbidden |    forbidden      | -           |
 
 ### Minimum object size
 
@@ -734,4 +728,4 @@ Delete operations resulting from application of lifecycle rules are not replicat
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).

pages/storage_and_backup/object_storage/s3_bucket_lifecycle/guide.en-asia.md

@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Smart Storage Management with Lifecycle Rules
 excerpt: Learn how to optimise your storage costs with OVHcloud lifecycle rules
-updated: 2025-05-13
+updated: 2025-06-05
 ---
 
 <style>
@@ -54,14 +54,7 @@ When an object reaches the end of its lifetime based on its lifecycle configurat
 - **versioned**: a delete marker is created and becomes the current version. You can also choose how many old versions you want to keep. If the current object version is the only object version and it is also a delete marker, that delete marker will be removed.
 - **versioning-suspended**: we currently do not allow for the suspension of versioning if you have a lifecycle configuration in effect and vice-versa. We currently do not allow for the upload of a lifecycle configuration if versioning is suspended on the bucket.
 
-> [!warning]
-> 
-> The release of the feature will be done in 2 phases:
->
-> - Phase 1: support for expiration only
-> - Phase 2: support for transitions
-
-## Expiration (available)
+## Expiration
 
 Lifecycle rules are processed asynchronously and on a best-effort basis. Most rules are applied within 24 hours, but for very large buckets or when processing many objects, it might take longer. During this delay, you continue to be billed for the object's current storage tier, even if the rule (e.g., expiration or transition) has already been triggered but not yet completed. For example, if an object is set to be deleted on day 30 but is only processed on day 32, you may be billed for an additional two days.
 
@@ -393,7 +386,7 @@ In a versioned bucket, the following configuration does the following actions:
 
 ///
 
-## Transition (coming soon)
+## Transition
 
 ### Supported transitions
 
@@ -403,11 +396,12 @@ In a versioned bucket, the following configuration does the following actions:
 
 The following are the currently supported transitions:
 
-| from/to          | High Performance | Standard  | Standard Infrequent Access |Cold Archive |
-| ---------------- | ---------------- | --------- | -------------------------- |------------ |
-| High Performance |        -         | yes       |             yes            | no          |
-| Standard         | forbidden        | -         |             yes            | no          |
-| Cold Archive     | forbidden        | forbidden |             forbidden      | -           |
+| from/to          | High Performance | Standard  | Infrequent Access |Cold Archive |
+| ---------------- | ---------------- | --------- | ----------------- |------------ |
+| High Performance |        -         | yes       |    yes            | no          |
+| Standard         | forbidden        | -         |    yes            | no          |
+| Infrequent Access| forbidden        | forbidden |    -              | no          |
+| Cold Archive     | forbidden        | forbidden |    forbidden      | -           |
 
 ### Minimum object size
 
@@ -734,4 +728,4 @@ Delete operations resulting from application of lifecycle rules are not replicat
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).

pages/storage_and_backup/object_storage/s3_bucket_lifecycle/guide.en-au.md

@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Smart Storage Management with Lifecycle Rules
 excerpt: Learn how to optimise your storage costs with OVHcloud lifecycle rules
-updated: 2025-05-13
+updated: 2025-06-05
 ---
 
 <style>
@@ -54,14 +54,7 @@ When an object reaches the end of its lifetime based on its lifecycle configurat
 - **versioned**: a delete marker is created and becomes the current version. You can also choose how many old versions you want to keep. If the current object version is the only object version and it is also a delete marker, that delete marker will be removed.
 - **versioning-suspended**: we currently do not allow for the suspension of versioning if you have a lifecycle configuration in effect and vice-versa. We currently do not allow for the upload of a lifecycle configuration if versioning is suspended on the bucket.
 
-> [!warning]
-> 
-> The release of the feature will be done in 2 phases:
->
-> - Phase 1: support for expiration only
-> - Phase 2: support for transitions
-
-## Expiration (available)
+## Expiration
 
 Lifecycle rules are processed asynchronously and on a best-effort basis. Most rules are applied within 24 hours, but for very large buckets or when processing many objects, it might take longer. During this delay, you continue to be billed for the object's current storage tier, even if the rule (e.g., expiration or transition) has already been triggered but not yet completed. For example, if an object is set to be deleted on day 30 but is only processed on day 32, you may be billed for an additional two days.
 
@@ -393,7 +386,7 @@ In a versioned bucket, the following configuration does the following actions:
 
 ///
 
-## Transition (coming soon)
+## Transition
 
 ### Supported transitions
 
@@ -403,11 +396,12 @@ In a versioned bucket, the following configuration does the following actions:
 
 The following are the currently supported transitions:
 
-| from/to          | High Performance | Standard  | Standard Infrequent Access |Cold Archive |
-| ---------------- | ---------------- | --------- | -------------------------- |------------ |
-| High Performance |        -         | yes       |             yes            | no          |
-| Standard         | forbidden        | -         |             yes            | no          |
-| Cold Archive     | forbidden        | forbidden |             forbidden      | -           |
+| from/to          | High Performance | Standard  | Infrequent Access |Cold Archive |
+| ---------------- | ---------------- | --------- | ----------------- |------------ |
+| High Performance |        -         | yes       |    yes            | no          |
+| Standard         | forbidden        | -         |    yes            | no          |
+| Infrequent Access| forbidden        | forbidden |    -              | no          |
+| Cold Archive     | forbidden        | forbidden |    forbidden      | -           |
 
 ### Minimum object size
 
@@ -734,4 +728,4 @@ Delete operations resulting from application of lifecycle rules are not replicat
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).

pages/storage_and_backup/object_storage/s3_bucket_lifecycle/guide.en-ca.md

@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Smart Storage Management with Lifecycle Rules
 excerpt: Learn how to optimise your storage costs with OVHcloud lifecycle rules
-updated: 2025-05-13
+updated: 2025-06-05
 ---
 
 <style>
@@ -54,14 +54,7 @@ When an object reaches the end of its lifetime based on its lifecycle configurat
 - **versioned**: a delete marker is created and becomes the current version. You can also choose how many old versions you want to keep. If the current object version is the only object version and it is also a delete marker, that delete marker will be removed.
 - **versioning-suspended**: we currently do not allow for the suspension of versioning if you have a lifecycle configuration in effect and vice-versa. We currently do not allow for the upload of a lifecycle configuration if versioning is suspended on the bucket.
 
-> [!warning]
-> 
-> The release of the feature will be done in 2 phases:
->
-> - Phase 1: support for expiration only
-> - Phase 2: support for transitions
-
-## Expiration (available)
+## Expiration
 
 Lifecycle rules are processed asynchronously and on a best-effort basis. Most rules are applied within 24 hours, but for very large buckets or when processing many objects, it might take longer. During this delay, you continue to be billed for the object's current storage tier, even if the rule (e.g., expiration or transition) has already been triggered but not yet completed. For example, if an object is set to be deleted on day 30 but is only processed on day 32, you may be billed for an additional two days.
 
@@ -393,7 +386,7 @@ In a versioned bucket, the following configuration does the following actions:
 
 ///
 
-## Transition (coming soon)
+## Transition
 
 ### Supported transitions
 
@@ -403,11 +396,12 @@ In a versioned bucket, the following configuration does the following actions:
 
 The following are the currently supported transitions:
 
-| from/to          | High Performance | Standard  | Standard Infrequent Access |Cold Archive |
-| ---------------- | ---------------- | --------- | -------------------------- |------------ |
-| High Performance |        -         | yes       |             yes            | no          |
-| Standard         | forbidden        | -         |             yes            | no          |
-| Cold Archive     | forbidden        | forbidden |             forbidden      | -           |
+| from/to          | High Performance | Standard  | Infrequent Access |Cold Archive |
+| ---------------- | ---------------- | --------- | ----------------- |------------ |
+| High Performance |        -         | yes       |    yes            | no          |
+| Standard         | forbidden        | -         |    yes            | no          |
+| Infrequent Access| forbidden        | forbidden |    -              | no          |
+| Cold Archive     | forbidden        | forbidden |    forbidden      | -           |
 
 ### Minimum object size
 
@@ -734,4 +728,4 @@ Delete operations resulting from application of lifecycle rules are not replicat
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).

pages/storage_and_backup/object_storage/s3_bucket_lifecycle/guide.en-gb.md

@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Smart Storage Management with Lifecycle Rules
 excerpt: Learn how to optimise your storage costs with OVHcloud lifecycle rules
-updated: 2025-05-13
+updated: 2025-06-05
 ---
 
 <style>
@@ -54,7 +54,6 @@ When an object reaches the end of its lifetime based on its lifecycle configurat
 - **versioned**: a delete marker is created and becomes the current version. You can also choose how many old versions you want to keep. If the current object version is the only object version and it is also a delete marker, that delete marker will be removed.
 - **versioning-suspended**: we currently do not allow for the suspension of versioning if you have a lifecycle configuration in effect and vice-versa. We currently do not allow for the upload of a lifecycle configuration if versioning is suspended on the bucket.
 
-
 ## Expiration
 
 Lifecycle rules are processed asynchronously and on a best-effort basis. Most rules are applied within 24 hours, but for very large buckets or when processing many objects, it might take longer. During this delay, you continue to be billed for the object's current storage tier, even if the rule (e.g., expiration or transition) has already been triggered but not yet completed. For example, if an object is set to be deleted on day 30 but is only processed on day 32, you may be billed for an additional two days.

pages/storage_and_backup/object_storage/s3_bucket_lifecycle/guide.en-ie.md

@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Smart Storage Management with Lifecycle Rules
 excerpt: Learn how to optimise your storage costs with OVHcloud lifecycle rules
-updated: 2025-05-13
+updated: 2025-06-05
 ---
 
 <style>
@@ -54,14 +54,7 @@ When an object reaches the end of its lifetime based on its lifecycle configurat
 - **versioned**: a delete marker is created and becomes the current version. You can also choose how many old versions you want to keep. If the current object version is the only object version and it is also a delete marker, that delete marker will be removed.
 - **versioning-suspended**: we currently do not allow for the suspension of versioning if you have a lifecycle configuration in effect and vice-versa. We currently do not allow for the upload of a lifecycle configuration if versioning is suspended on the bucket.
 
-> [!warning]
-> 
-> The release of the feature will be done in 2 phases:
->
-> - Phase 1: support for expiration only
-> - Phase 2: support for transitions
-
-## Expiration (available)
+## Expiration
 
 Lifecycle rules are processed asynchronously and on a best-effort basis. Most rules are applied within 24 hours, but for very large buckets or when processing many objects, it might take longer. During this delay, you continue to be billed for the object's current storage tier, even if the rule (e.g., expiration or transition) has already been triggered but not yet completed. For example, if an object is set to be deleted on day 30 but is only processed on day 32, you may be billed for an additional two days.
 
@@ -393,7 +386,7 @@ In a versioned bucket, the following configuration does the following actions:
 
 ///
 
-## Transition (coming soon)
+## Transition
 
 ### Supported transitions
 
@@ -403,11 +396,12 @@ In a versioned bucket, the following configuration does the following actions:
 
 The following are the currently supported transitions:
 
-| from/to          | High Performance | Standard  | Standard Infrequent Access |Cold Archive |
-| ---------------- | ---------------- | --------- | -------------------------- |------------ |
-| High Performance |        -         | yes       |             yes            | no          |
-| Standard         | forbidden        | -         |             yes            | no          |
-| Cold Archive     | forbidden        | forbidden |             forbidden      | -           |
+| from/to          | High Performance | Standard  | Infrequent Access |Cold Archive |
+| ---------------- | ---------------- | --------- | ----------------- |------------ |
+| High Performance |        -         | yes       |    yes            | no          |
+| Standard         | forbidden        | -         |    yes            | no          |
+| Infrequent Access| forbidden        | forbidden |    -              | no          |
+| Cold Archive     | forbidden        | forbidden |    forbidden      | -           |
 
 ### Minimum object size
 
@@ -734,4 +728,4 @@ Delete operations resulting from application of lifecycle rules are not replicat
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).