diff --git a/docs/de/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx b/docs/de/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx index c612fb39..69be0750 100644 --- a/docs/de/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx +++ b/docs/de/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx @@ -1,7 +1,7 @@ --- title: Object Storage - Smart Storage Management with Lifecycle Rules description: Learn how to optimise your OVHcloud Object Storage costs by configuring lifecycle rules for automatic expiration, transition, and cleanup of objects -lastUpdated: 2026-04-08 +lastUpdated: 2026-05-25 --- @@ -764,7 +764,67 @@ aws s3api put-bucket-lifecycle-configuration --bucket my-bucket --lifecycle-conf -### Using the OVHcloud Control Panel (coming soon) +### Using the OVHcloud Control Panel + +As a prerequisite, you must have a bucket containing data on which you want to apply the lifecycle configuration. + +**Step 1 — Navigate to your bucket's Lifecycle tab.** + +Log in to the OVHcloud Control Panel, open the Public Cloud section, and select your project. In the left-hand menu, click Object Storage under **Storage**, then click the name of the target bucket. Go to the Lifecycle tab and click Create rule. + +**Step 2 — Configure the rule identifier.** + +Enter a unique name in the **Rule identifier** field. + +**Step 3 — Define the rule scope.** + +Choose whether the rule applies to all objects or only to specific ones: + +- Apply to all objects in the container: the rule applies to every object in the bucket. +- Limit the application of this rule: reveals additional filter fields: + - **Prefix**: restrict the rule to objects whose key starts with a given prefix (e.g. `logs/`). + - **Tags**: click + Add a tag to filter by one or more key/value object tags. + - **Specify a minimum object size**: optionally set a minimum size threshold. + - **Specify a maximum object size**: optionally set a maximum size threshold. + +**Step 4 — Select lifecycle operations.** + +Tick one or more checkboxes to enable operations. Each checkbox reveals its configuration fields: + +- **Transition the current version of objects**: automate transition of current versions to a lower-cost storage tier. + - **Days after creation**: number of days after object creation before the transition is triggered (minimum: 30). + - **Storage class**: select the target storage class. + - Click + Add a transition to add multiple transition steps. + +- **Expire the current version of objects**: automatically delete current object versions after a set period. + - **Days after creation**: number of days after object creation before deletion. + +- **Delete expired delete markers**: remove delete markers that have no remaining non-current versions. No additional fields required. + +- **Transition older versions of objects**: automate transition of non-current versions to a lower-cost storage tier. + - **Days after becoming non-current**: minimum age of a non-current version before the transition is triggered (minimum: 30). + - **Storage class**: select the target storage class. + - **Non-current versions to keep**: number of the most recent non-current versions to retain in their current tier (0 means no retention limit applies). + - Click + Add a transition to add multiple transition steps. + +- **Expiration of non-current versions**: automatically delete non-current object versions. + - **Days after becoming non-current**: minimum age of a non-current version before deletion. + - **Non-current versions to keep**: number of the most recent non-current versions to retain before deletion applies. + +- **Delete incomplete multipart uploads**: stop and delete parts of incomplete multipart uploads. + - **Days after initiation**: number of days after the upload was initiated before its parts are deleted (must be greater than 0). + +**Step 5 — Create the rule.** + +Once all required fields are filled in, click Create rule. The rule appears in the lifecycle rules list and is applied asynchronously within 24 hours. + +**Managing existing rules.** + +From the lifecycle rules list, click the ... button at the end of a rule's row to access the following actions: + +- **Modify**: edit the rule's scope, filters, or operations. +- **Enable/Disable**: toggle the rule on or off without deleting it. +- **Delete**: permanently remove the rule. ## FAQ @@ -807,7 +867,7 @@ Delete operations resulting from application of lifecycle rules are not replicat ## Go further -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/de/professional-services/) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. +If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-gb/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](https://community.ovhcloud.com/community/en). diff --git a/docs/en/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx b/docs/en/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx index f56f0576..69be0750 100644 --- a/docs/en/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx +++ b/docs/en/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx @@ -1,7 +1,7 @@ --- title: Object Storage - Smart Storage Management with Lifecycle Rules description: Learn how to optimise your OVHcloud Object Storage costs by configuring lifecycle rules for automatic expiration, transition, and cleanup of objects -lastUpdated: 2026-04-08 +lastUpdated: 2026-05-25 --- @@ -764,7 +764,67 @@ aws s3api put-bucket-lifecycle-configuration --bucket my-bucket --lifecycle-conf -### Using the OVHcloud Control Panel (coming soon) +### Using the OVHcloud Control Panel + +As a prerequisite, you must have a bucket containing data on which you want to apply the lifecycle configuration. + +**Step 1 — Navigate to your bucket's Lifecycle tab.** + +Log in to the OVHcloud Control Panel, open the Public Cloud section, and select your project. In the left-hand menu, click Object Storage under **Storage**, then click the name of the target bucket. Go to the Lifecycle tab and click Create rule. + +**Step 2 — Configure the rule identifier.** + +Enter a unique name in the **Rule identifier** field. + +**Step 3 — Define the rule scope.** + +Choose whether the rule applies to all objects or only to specific ones: + +- Apply to all objects in the container: the rule applies to every object in the bucket. +- Limit the application of this rule: reveals additional filter fields: + - **Prefix**: restrict the rule to objects whose key starts with a given prefix (e.g. `logs/`). + - **Tags**: click + Add a tag to filter by one or more key/value object tags. + - **Specify a minimum object size**: optionally set a minimum size threshold. + - **Specify a maximum object size**: optionally set a maximum size threshold. + +**Step 4 — Select lifecycle operations.** + +Tick one or more checkboxes to enable operations. Each checkbox reveals its configuration fields: + +- **Transition the current version of objects**: automate transition of current versions to a lower-cost storage tier. + - **Days after creation**: number of days after object creation before the transition is triggered (minimum: 30). + - **Storage class**: select the target storage class. + - Click + Add a transition to add multiple transition steps. + +- **Expire the current version of objects**: automatically delete current object versions after a set period. + - **Days after creation**: number of days after object creation before deletion. + +- **Delete expired delete markers**: remove delete markers that have no remaining non-current versions. No additional fields required. + +- **Transition older versions of objects**: automate transition of non-current versions to a lower-cost storage tier. + - **Days after becoming non-current**: minimum age of a non-current version before the transition is triggered (minimum: 30). + - **Storage class**: select the target storage class. + - **Non-current versions to keep**: number of the most recent non-current versions to retain in their current tier (0 means no retention limit applies). + - Click + Add a transition to add multiple transition steps. + +- **Expiration of non-current versions**: automatically delete non-current object versions. + - **Days after becoming non-current**: minimum age of a non-current version before deletion. + - **Non-current versions to keep**: number of the most recent non-current versions to retain before deletion applies. + +- **Delete incomplete multipart uploads**: stop and delete parts of incomplete multipart uploads. + - **Days after initiation**: number of days after the upload was initiated before its parts are deleted (must be greater than 0). + +**Step 5 — Create the rule.** + +Once all required fields are filled in, click Create rule. The rule appears in the lifecycle rules list and is applied asynchronously within 24 hours. + +**Managing existing rules.** + +From the lifecycle rules list, click the ... button at the end of a rule's row to access the following actions: + +- **Modify**: edit the rule's scope, filters, or operations. +- **Enable/Disable**: toggle the rule on or off without deleting it. +- **Delete**: permanently remove the rule. ## FAQ diff --git a/docs/es/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx b/docs/es/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx index e0b8fb83..69be0750 100644 --- a/docs/es/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx +++ b/docs/es/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx @@ -1,7 +1,7 @@ --- title: Object Storage - Smart Storage Management with Lifecycle Rules description: Learn how to optimise your OVHcloud Object Storage costs by configuring lifecycle rules for automatic expiration, transition, and cleanup of objects -lastUpdated: 2026-04-08 +lastUpdated: 2026-05-25 --- @@ -764,7 +764,67 @@ aws s3api put-bucket-lifecycle-configuration --bucket my-bucket --lifecycle-conf -### Using the OVHcloud Control Panel (coming soon) +### Using the OVHcloud Control Panel + +As a prerequisite, you must have a bucket containing data on which you want to apply the lifecycle configuration. + +**Step 1 — Navigate to your bucket's Lifecycle tab.** + +Log in to the OVHcloud Control Panel, open the Public Cloud section, and select your project. In the left-hand menu, click Object Storage under **Storage**, then click the name of the target bucket. Go to the Lifecycle tab and click Create rule. + +**Step 2 — Configure the rule identifier.** + +Enter a unique name in the **Rule identifier** field. + +**Step 3 — Define the rule scope.** + +Choose whether the rule applies to all objects or only to specific ones: + +- Apply to all objects in the container: the rule applies to every object in the bucket. +- Limit the application of this rule: reveals additional filter fields: + - **Prefix**: restrict the rule to objects whose key starts with a given prefix (e.g. `logs/`). + - **Tags**: click + Add a tag to filter by one or more key/value object tags. + - **Specify a minimum object size**: optionally set a minimum size threshold. + - **Specify a maximum object size**: optionally set a maximum size threshold. + +**Step 4 — Select lifecycle operations.** + +Tick one or more checkboxes to enable operations. Each checkbox reveals its configuration fields: + +- **Transition the current version of objects**: automate transition of current versions to a lower-cost storage tier. + - **Days after creation**: number of days after object creation before the transition is triggered (minimum: 30). + - **Storage class**: select the target storage class. + - Click + Add a transition to add multiple transition steps. + +- **Expire the current version of objects**: automatically delete current object versions after a set period. + - **Days after creation**: number of days after object creation before deletion. + +- **Delete expired delete markers**: remove delete markers that have no remaining non-current versions. No additional fields required. + +- **Transition older versions of objects**: automate transition of non-current versions to a lower-cost storage tier. + - **Days after becoming non-current**: minimum age of a non-current version before the transition is triggered (minimum: 30). + - **Storage class**: select the target storage class. + - **Non-current versions to keep**: number of the most recent non-current versions to retain in their current tier (0 means no retention limit applies). + - Click + Add a transition to add multiple transition steps. + +- **Expiration of non-current versions**: automatically delete non-current object versions. + - **Days after becoming non-current**: minimum age of a non-current version before deletion. + - **Non-current versions to keep**: number of the most recent non-current versions to retain before deletion applies. + +- **Delete incomplete multipart uploads**: stop and delete parts of incomplete multipart uploads. + - **Days after initiation**: number of days after the upload was initiated before its parts are deleted (must be greater than 0). + +**Step 5 — Create the rule.** + +Once all required fields are filled in, click Create rule. The rule appears in the lifecycle rules list and is applied asynchronously within 24 hours. + +**Managing existing rules.** + +From the lifecycle rules list, click the ... button at the end of a rule's row to access the following actions: + +- **Modify**: edit the rule's scope, filters, or operations. +- **Enable/Disable**: toggle the rule on or off without deleting it. +- **Delete**: permanently remove the rule. ## FAQ @@ -807,7 +867,7 @@ Delete operations resulting from application of lifecycle rules are not replicat ## Go further -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/es-es/professional-services/) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. +If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-gb/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](https://community.ovhcloud.com/community/en). diff --git a/docs/fr/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx b/docs/fr/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx index 1029044d..73576ba1 100644 --- a/docs/fr/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx +++ b/docs/fr/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx @@ -1,7 +1,7 @@ --- title: Object Storage - Gestion intelligente du stockage avec des règles lifecycle description: "Découvrez comment optimiser vos coûts de stockage avec les règles lifecycle d'OVHcloud" -lastUpdated: 2026-04-08 +lastUpdated: 2026-05-25 --- @@ -764,7 +764,67 @@ aws s3api put-bucket-lifecycle-configuration --bucket my-bucket --lifecycle-conf -### Via l'espace client OVHcloud (à venir) +### Via l'espace client OVHcloud + +Comme prérequis, vous devez avoir un bucket contenant des données sur lesquelles vous souhaitez appliquer la configuration de lifecycle. + +**Étape 1 — Accédez à l'onglet Lifecycle de votre bucket.** + +Connectez-vous à votre espace client OVHcloud, ouvrez la section Public Cloud et sélectionnez votre projet. Dans le menu de gauche, cliquez sur Object Storage sous **Storage**, puis cliquez sur le nom du bucket cible. Accédez à l'onglet Lifecycle et cliquez sur Créer une règle. + +**Étape 2 — Configurez l'identifiant de la règle.** + +Saisissez un nom unique dans le champ **Identifiant de la règle**. + +**Étape 3 — Définissez la portée de la règle.** + +Choisissez si la règle s'applique à tous les objets ou uniquement à des objets spécifiques : + +- Appliquer à tous les objets du conteneur : la règle s'applique à tous les objets du bucket. +- Limiter l'application de cette règle : affiche des champs de filtre supplémentaires : + - **Préfixe** : restreignez la règle aux objets dont la clé commence par un préfixe donné (ex. `logs/`). + - **Tags** : cliquez sur + Ajouter un tag pour filtrer par un ou plusieurs tags clé/valeur. + - **Spécifier une taille minimale d'objet** : définissez optionnellement un seuil de taille minimale. + - **Spécifier une taille maximale d'objet** : définissez optionnellement un seuil de taille maximale. + +**Étape 4 — Sélectionnez les opérations de lifecycle.** + +Cochez une ou plusieurs cases pour activer des opérations. Chaque case révèle ses champs de configuration : + +- **Transition de la version courante des objets** : automatise la transition des versions courantes vers un niveau de stockage moins coûteux. + - **Jours après la création** : nombre de jours après la création de l'objet avant que la transition ne soit déclenchée (minimum : 30). + - **Classe de stockage** : sélectionnez la classe de stockage cible. + - Cliquez sur + Ajouter une transition pour ajouter plusieurs étapes de transition. + +- **Expiration de la version courante des objets** : supprime automatiquement les versions courantes des objets après une période définie. + - **Jours après la création** : nombre de jours après la création de l'objet avant la suppression. + +- **Suppression des marqueurs de suppression expirés** : supprime les marqueurs de suppression qui n'ont plus aucune version non courante. Aucun champ supplémentaire requis. + +- **Transition des versions non courantes des objets** : automatise la transition des versions non courantes vers un niveau de stockage moins coûteux. + - **Jours après être devenu non courant** : âge minimum d'une version non courante avant que la transition ne soit déclenchée (minimum : 30). + - **Classe de stockage** : sélectionnez la classe de stockage cible. + - **Versions non courantes à conserver** : nombre des versions non courantes les plus récentes à conserver dans leur niveau de stockage actuel (0 signifie qu'aucune limite de conservation ne s'applique). + - Cliquez sur + Ajouter une transition pour ajouter plusieurs étapes de transition. + +- **Expiration des versions non courantes** : supprime automatiquement les versions non courantes des objets. + - **Jours après être devenu non courant** : âge minimum d'une version non courante avant la suppression. + - **Versions non courantes à conserver** : nombre des versions non courantes les plus récentes à conserver avant que la suppression ne s'applique. + +- **Suppression des téléversements multi-parties incomplets** : arrête et supprime les parties des téléversements multi-parties incomplets. + - **Jours après l'initiation** : nombre de jours après le lancement du téléversement avant que ses parties soient supprimées (doit être supérieur à 0). + +**Étape 5 — Créez la règle.** + +Une fois tous les champs requis remplis, cliquez sur Créer une règle. La règle apparaît dans la liste des règles de lifecycle et est appliquée de manière asynchrone dans les 24 heures. + +**Gestion des règles existantes.** + +Depuis la liste des règles de lifecycle, cliquez sur le bouton ... à la fin de la ligne d'une règle pour accéder aux actions suivantes : + +- **Modifier** : modifiez la portée, les filtres ou les opérations de la règle. +- **Activer/Désactiver** : activez ou désactivez la règle sans la supprimer. +- **Supprimer** : supprimez définitivement la règle. ## FAQ diff --git a/docs/it/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx b/docs/it/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx index 1efee06d..69be0750 100644 --- a/docs/it/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx +++ b/docs/it/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx @@ -1,7 +1,7 @@ --- title: Object Storage - Smart Storage Management with Lifecycle Rules description: Learn how to optimise your OVHcloud Object Storage costs by configuring lifecycle rules for automatic expiration, transition, and cleanup of objects -lastUpdated: 2026-04-08 +lastUpdated: 2026-05-25 --- @@ -764,7 +764,67 @@ aws s3api put-bucket-lifecycle-configuration --bucket my-bucket --lifecycle-conf -### Using the OVHcloud Control Panel (coming soon) +### Using the OVHcloud Control Panel + +As a prerequisite, you must have a bucket containing data on which you want to apply the lifecycle configuration. + +**Step 1 — Navigate to your bucket's Lifecycle tab.** + +Log in to the OVHcloud Control Panel, open the Public Cloud section, and select your project. In the left-hand menu, click Object Storage under **Storage**, then click the name of the target bucket. Go to the Lifecycle tab and click Create rule. + +**Step 2 — Configure the rule identifier.** + +Enter a unique name in the **Rule identifier** field. + +**Step 3 — Define the rule scope.** + +Choose whether the rule applies to all objects or only to specific ones: + +- Apply to all objects in the container: the rule applies to every object in the bucket. +- Limit the application of this rule: reveals additional filter fields: + - **Prefix**: restrict the rule to objects whose key starts with a given prefix (e.g. `logs/`). + - **Tags**: click + Add a tag to filter by one or more key/value object tags. + - **Specify a minimum object size**: optionally set a minimum size threshold. + - **Specify a maximum object size**: optionally set a maximum size threshold. + +**Step 4 — Select lifecycle operations.** + +Tick one or more checkboxes to enable operations. Each checkbox reveals its configuration fields: + +- **Transition the current version of objects**: automate transition of current versions to a lower-cost storage tier. + - **Days after creation**: number of days after object creation before the transition is triggered (minimum: 30). + - **Storage class**: select the target storage class. + - Click + Add a transition to add multiple transition steps. + +- **Expire the current version of objects**: automatically delete current object versions after a set period. + - **Days after creation**: number of days after object creation before deletion. + +- **Delete expired delete markers**: remove delete markers that have no remaining non-current versions. No additional fields required. + +- **Transition older versions of objects**: automate transition of non-current versions to a lower-cost storage tier. + - **Days after becoming non-current**: minimum age of a non-current version before the transition is triggered (minimum: 30). + - **Storage class**: select the target storage class. + - **Non-current versions to keep**: number of the most recent non-current versions to retain in their current tier (0 means no retention limit applies). + - Click + Add a transition to add multiple transition steps. + +- **Expiration of non-current versions**: automatically delete non-current object versions. + - **Days after becoming non-current**: minimum age of a non-current version before deletion. + - **Non-current versions to keep**: number of the most recent non-current versions to retain before deletion applies. + +- **Delete incomplete multipart uploads**: stop and delete parts of incomplete multipart uploads. + - **Days after initiation**: number of days after the upload was initiated before its parts are deleted (must be greater than 0). + +**Step 5 — Create the rule.** + +Once all required fields are filled in, click Create rule. The rule appears in the lifecycle rules list and is applied asynchronously within 24 hours. + +**Managing existing rules.** + +From the lifecycle rules list, click the ... button at the end of a rule's row to access the following actions: + +- **Modify**: edit the rule's scope, filters, or operations. +- **Enable/Disable**: toggle the rule on or off without deleting it. +- **Delete**: permanently remove the rule. ## FAQ @@ -807,7 +867,7 @@ Delete operations resulting from application of lifecycle rules are not replicat ## Go further -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/it/professional-services/) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. +If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-gb/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](https://community.ovhcloud.com/community/en). diff --git a/docs/pl/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx b/docs/pl/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx index d6101553..69be0750 100644 --- a/docs/pl/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx +++ b/docs/pl/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx @@ -1,7 +1,7 @@ --- title: Object Storage - Smart Storage Management with Lifecycle Rules description: Learn how to optimise your OVHcloud Object Storage costs by configuring lifecycle rules for automatic expiration, transition, and cleanup of objects -lastUpdated: 2026-04-08 +lastUpdated: 2026-05-25 --- @@ -764,7 +764,67 @@ aws s3api put-bucket-lifecycle-configuration --bucket my-bucket --lifecycle-conf -### Using the OVHcloud Control Panel (coming soon) +### Using the OVHcloud Control Panel + +As a prerequisite, you must have a bucket containing data on which you want to apply the lifecycle configuration. + +**Step 1 — Navigate to your bucket's Lifecycle tab.** + +Log in to the OVHcloud Control Panel, open the Public Cloud section, and select your project. In the left-hand menu, click Object Storage under **Storage**, then click the name of the target bucket. Go to the Lifecycle tab and click Create rule. + +**Step 2 — Configure the rule identifier.** + +Enter a unique name in the **Rule identifier** field. + +**Step 3 — Define the rule scope.** + +Choose whether the rule applies to all objects or only to specific ones: + +- Apply to all objects in the container: the rule applies to every object in the bucket. +- Limit the application of this rule: reveals additional filter fields: + - **Prefix**: restrict the rule to objects whose key starts with a given prefix (e.g. `logs/`). + - **Tags**: click + Add a tag to filter by one or more key/value object tags. + - **Specify a minimum object size**: optionally set a minimum size threshold. + - **Specify a maximum object size**: optionally set a maximum size threshold. + +**Step 4 — Select lifecycle operations.** + +Tick one or more checkboxes to enable operations. Each checkbox reveals its configuration fields: + +- **Transition the current version of objects**: automate transition of current versions to a lower-cost storage tier. + - **Days after creation**: number of days after object creation before the transition is triggered (minimum: 30). + - **Storage class**: select the target storage class. + - Click + Add a transition to add multiple transition steps. + +- **Expire the current version of objects**: automatically delete current object versions after a set period. + - **Days after creation**: number of days after object creation before deletion. + +- **Delete expired delete markers**: remove delete markers that have no remaining non-current versions. No additional fields required. + +- **Transition older versions of objects**: automate transition of non-current versions to a lower-cost storage tier. + - **Days after becoming non-current**: minimum age of a non-current version before the transition is triggered (minimum: 30). + - **Storage class**: select the target storage class. + - **Non-current versions to keep**: number of the most recent non-current versions to retain in their current tier (0 means no retention limit applies). + - Click + Add a transition to add multiple transition steps. + +- **Expiration of non-current versions**: automatically delete non-current object versions. + - **Days after becoming non-current**: minimum age of a non-current version before deletion. + - **Non-current versions to keep**: number of the most recent non-current versions to retain before deletion applies. + +- **Delete incomplete multipart uploads**: stop and delete parts of incomplete multipart uploads. + - **Days after initiation**: number of days after the upload was initiated before its parts are deleted (must be greater than 0). + +**Step 5 — Create the rule.** + +Once all required fields are filled in, click Create rule. The rule appears in the lifecycle rules list and is applied asynchronously within 24 hours. + +**Managing existing rules.** + +From the lifecycle rules list, click the ... button at the end of a rule's row to access the following actions: + +- **Modify**: edit the rule's scope, filters, or operations. +- **Enable/Disable**: toggle the rule on or off without deleting it. +- **Delete**: permanently remove the rule. ## FAQ @@ -807,7 +867,7 @@ Delete operations resulting from application of lifecycle rules are not replicat ## Go further -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/pl/professional-services/) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. +If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-gb/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](https://community.ovhcloud.com/community/en). diff --git a/docs/pt/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx b/docs/pt/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx index 5249b11d..69be0750 100644 --- a/docs/pt/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx +++ b/docs/pt/guides/storage-and-backup/object-storage/s3-bucket-lifecycle.mdx @@ -1,7 +1,7 @@ --- title: Object Storage - Smart Storage Management with Lifecycle Rules description: Learn how to optimise your OVHcloud Object Storage costs by configuring lifecycle rules for automatic expiration, transition, and cleanup of objects -lastUpdated: 2026-04-08 +lastUpdated: 2026-05-25 --- @@ -764,7 +764,67 @@ aws s3api put-bucket-lifecycle-configuration --bucket my-bucket --lifecycle-conf -### Using the OVHcloud Control Panel (coming soon) +### Using the OVHcloud Control Panel + +As a prerequisite, you must have a bucket containing data on which you want to apply the lifecycle configuration. + +**Step 1 — Navigate to your bucket's Lifecycle tab.** + +Log in to the OVHcloud Control Panel, open the Public Cloud section, and select your project. In the left-hand menu, click Object Storage under **Storage**, then click the name of the target bucket. Go to the Lifecycle tab and click Create rule. + +**Step 2 — Configure the rule identifier.** + +Enter a unique name in the **Rule identifier** field. + +**Step 3 — Define the rule scope.** + +Choose whether the rule applies to all objects or only to specific ones: + +- Apply to all objects in the container: the rule applies to every object in the bucket. +- Limit the application of this rule: reveals additional filter fields: + - **Prefix**: restrict the rule to objects whose key starts with a given prefix (e.g. `logs/`). + - **Tags**: click + Add a tag to filter by one or more key/value object tags. + - **Specify a minimum object size**: optionally set a minimum size threshold. + - **Specify a maximum object size**: optionally set a maximum size threshold. + +**Step 4 — Select lifecycle operations.** + +Tick one or more checkboxes to enable operations. Each checkbox reveals its configuration fields: + +- **Transition the current version of objects**: automate transition of current versions to a lower-cost storage tier. + - **Days after creation**: number of days after object creation before the transition is triggered (minimum: 30). + - **Storage class**: select the target storage class. + - Click + Add a transition to add multiple transition steps. + +- **Expire the current version of objects**: automatically delete current object versions after a set period. + - **Days after creation**: number of days after object creation before deletion. + +- **Delete expired delete markers**: remove delete markers that have no remaining non-current versions. No additional fields required. + +- **Transition older versions of objects**: automate transition of non-current versions to a lower-cost storage tier. + - **Days after becoming non-current**: minimum age of a non-current version before the transition is triggered (minimum: 30). + - **Storage class**: select the target storage class. + - **Non-current versions to keep**: number of the most recent non-current versions to retain in their current tier (0 means no retention limit applies). + - Click + Add a transition to add multiple transition steps. + +- **Expiration of non-current versions**: automatically delete non-current object versions. + - **Days after becoming non-current**: minimum age of a non-current version before deletion. + - **Non-current versions to keep**: number of the most recent non-current versions to retain before deletion applies. + +- **Delete incomplete multipart uploads**: stop and delete parts of incomplete multipart uploads. + - **Days after initiation**: number of days after the upload was initiated before its parts are deleted (must be greater than 0). + +**Step 5 — Create the rule.** + +Once all required fields are filled in, click Create rule. The rule appears in the lifecycle rules list and is applied asynchronously within 24 hours. + +**Managing existing rules.** + +From the lifecycle rules list, click the ... button at the end of a rule's row to access the following actions: + +- **Modify**: edit the rule's scope, filters, or operations. +- **Enable/Disable**: toggle the rule on or off without deleting it. +- **Delete**: permanently remove the rule. ## FAQ @@ -807,7 +867,7 @@ Delete operations resulting from application of lifecycle rules are not replicat ## Go further -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/pt/professional-services/) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. +If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-gb/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](https://community.ovhcloud.com/community/en).