Object Storage - S3 compatible updates - EN/FR

Author: Y0Coss

Diff for: pages/storage_and_backup/object_storage/cold_archive_faq/guide.en-gb.md

@@ -14,7 +14,7 @@ The Cold Archive storage class is an Object Storage service adapted for long-ter
 - Strengthening resilience plans, implementing a 3+2+1 strategy.
 - Large storage of video/photo media.
 
-This storage class, easily accessible via S3 API, is recommended if your data is stored for more than 6 months without any particular need for restoration (less than one restoration per year).
+This storage class, easily accessible via S3 **\*** compatible API, is recommended if your data is stored for more than 6 months without any particular need for restoration (less than one restoration per year).
 
 Its design is highly resilient (4 datacentres), low cost, sustainable (the lifespan of a *tape* is 16 years). However, you will need to wait 48 hours for a request to restore your data.
 
@@ -26,11 +26,11 @@ To use the service, you will need to meet the following requirements:
 
 - You must have a [Public Cloud project](/pages/public_cloud/compute/create_a_public_cloud_project) in your OVHcloud account. 
 - You must be logged in to your [OVHcloud Control Panel](/links/manager).
-- You must have created a [S3 user](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage).
+- You must have createdn a [Object Storage user](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage).
 
-### What S3 features are available with the Cold Archive storage class? 
+### What features are available with the Cold Archive storage class?
 
-All the features of our Object Storage - S3 API storage classes are supported by the Cold Archive service. You can find the list of functions on [this page](/pages/storage_and_backup/object_storage/s3_s3_compliancy).
+All the features of our Object Storage storage classes are supported by the Cold Archive service. You can find the list of functions on [this page](/pages/storage_and_backup/object_storage/s3_s3_compliancy).
 
 Two features have been disabled (versioning and object lock) because, by design, an archived object container has a single version that cannot be modified.
 
@@ -46,11 +46,11 @@ Please use the endpoint corresponding to this service: [https://s3.rbx-archive.i
 
 After it is created, a bucket is read/write.
 
-You can then upload files to this container via S3 API, CLI or SDK.
+You can then upload files to this container via the S3 compatible API, CLI or SDK.
 
 ### How do I archive a container?
 
-You archive the container from your user interface, via S3 API, CLI or SDK. 
+You archive the container from your user interface, via the S3 compatible API, CLI or SDK. 
 
 In the user interface, the action is carried out by activating the `Archive`{.action} button. 
 
@@ -109,7 +109,7 @@ This is why the SLA is at 48h although in reality the time can sometimes be much
 
 Yes, you can use the Cold Archive storage class to archive your data which has been backed-up with another cloud provider.
 
-For example, you install a server and set Rclone to synchronize your files from an Object Storage S3 (third-party cloud provider) to OVHcloud S3 Object Storage, following this guide: [Object Storage - Use S3 Object Storage with Rclone](/pages/storage_and_backup/object_storage/s3_rclone).
+For example, you install a server and set Rclone to synchronize your files from an Object Storage (third-party cloud provider) to OVHcloud Object Storage, following this guide: [Object Storage - Use Object Storage with Rclone](/pages/storage_and_backup/object_storage/s3_rclone).
 
 ### How do I download large volumes?
 
@@ -131,7 +131,7 @@ We do not offer this service. Archives are stored in *off-line* magnetic tapes,
 
 Billing is done on a volume basis in GB per hour.
 
-During the download phase, your storage volumes are billed at the price of the **Standard object storage - S3 API** storage class.
+During the download phase, your storage volumes are billed at the price of the **Object Storage - Standard** class.
 
 After archiving the container (*put-archive*), your data volumes are billed at the price of the **Cold Archive** storage class.
 
@@ -196,7 +196,7 @@ OVHcloud offers a managed service. OVHcloud takes care of the replacement of mag
 
 ### Can I protect my data in transit?
 
-To protect data against theft, the connection between an S3 object storage (*from*) and OVHcloud object storage (*to*) is encrypted and protected by https.
+To protect data against theft, the connection between a third-party object storage (*from*) and OVHcloud Object Storage (*to*) is encrypted and protected by https.
 
 In addition, we recommend that you encrypt your data before sending it.
 
@@ -213,15 +213,15 @@ You have 4 levels of credentials:
 - The admin user (commonly known as *NIC admin*) 
 - The billing user (commonly known as *NIC billing*)
 - The OpenStack user
-- An S3 user
+- An Object user
 
 | ID | Role |
 | --- | --- |
 | NIC admin | Administrator<br>Billing |
 | NIC billing | Billing |
 | NIC technical | Administrator |
 | OpenStack user | (1) Administrator<br>(2) Object Storage |
-| S3 user (S3 credentials) | 4 roles<br>(1) Administrator<br>(2) Read only<br>(3) Read<br>(4) Deny<br><br>Only the administrator role has access to tiering actions (archive, delete, restore) |
+| Object Storage user (Object Storage credentials) | 4 roles<br>(1) Administrator<br>(2) Read only<br>(3) Read<br>(4) Deny<br><br>Only the administrator role has access to tiering actions (archive, delete, restore) |
 
 ## Resilience
 
@@ -237,7 +237,7 @@ The redundancy of the data is done by an 8+4 Erasure Coding mechanism. Data can
 
 The service’s SLA is available on [this page](/links/terms-conditions-contracts).
 
-It corresponds to the availability of the Object Storage service (RBX-archive endpoint) at 99.9% and the associated features (S3 API and tiering).
+It corresponds to the availability of the Object Storage service (RBX-archive endpoint) at 99.9% and the associated features (S3 compatible API and tiering).
 
 ## Go further
 

Diff for: pages/storage_and_backup/object_storage/cold_archive_faq/guide.fr-fr.md

@@ -14,7 +14,7 @@ La classe de stockage « Cold Archive » est un service de stockage objet (*Ob
 - renforcement de plan de résilience, mise en place d'une stratégie 3+2+1 ;
 - stockage volumineux de media vidéos, photo.
 
-Cette classe de stockage, facilement accessible par API S3, est recommandée si vos données sont stockées pour une durée supérieure à 6 mois sans besoin particulier de restauration (moins d'une restauration par an).
+Cette classe de stockage, facilement accessible par API compatible S3 **\***, est recommandée si vos données sont stockées pour une durée supérieure à 6 mois sans besoin particulier de restauration (moins d'une restauration par an).
 
 Son design est hautement résilient (4 datacentres), à bas coût, durable (la durée de vie d'une *tape* est de 16 ans). En contrepartie, il vous faudra patienter 48 heures lors d'une demande de restauration des données.
 
@@ -26,11 +26,11 @@ Pour utiliser le service, les prérequis sont les suivants :
 
 - Avoir un [projet Public Cloud](/pages/public_cloud/compute/create_a_public_cloud_project) dans votre compte OVHcloud. 
 - Etre connecté à votre [espace client OVHcloud](/links/manager).
-- Avoir créé un [utilisateur S3](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage).
+- Avoir créé un [utilisateur Object Storage](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage).
 
-### Quelles sont les fonctions S3 disponibles avec la classe de stockage Cold Archive ? 
+### Quelles sont les fonctions disponibles avec la classe de stockage Cold Archive ?
 
-L'ensemble des fonctionnalités de nos classes de stockages Object Storage - S3 API sont supportées par le service Cold Archive. Vous trouverez la liste des fonctions sur [cette page](/pages/storage_and_backup/object_storage/s3_s3_compliancy).
+L'ensemble des fonctionnalités de nos classes de stockages Object Storage sont supportées par le service Cold Archive. Vous trouverez la liste des fonctions sur [cette page](/pages/storage_and_backup/object_storage/s3_s3_compliancy).
 
 Deux fonctions ont été désactivées (versioning et object lock) car, par design, un conteneur d'objets archivé a une seule version qui ne peut pas être modifiée.
 
@@ -46,11 +46,11 @@ Veillez à utiliser l'endpoint correspondant à ce service : [https://s3.rbx-arc
 
 Après sa création, un bucket est en lecture / écriture.
 
-Vous téléversez ensuite des fichiers dans ce conteneur par API S3, CLI ou SDK.
+Vous téléversez ensuite des fichiers dans ce conteneur via l'API compatible S3, CLI ou SDK.
 
 ### Comment archiver un conteneur ?
 
-Vous archivez le conteneur depuis votre interface utilisateur, par API S3, CLI ou SDK. 
+Vous archivez le conteneur depuis votre interface utilisateur,via l'API compatible S3, CLI ou SDK. 
 
 Dans l'interface utilisateur, l'action est réalisée en activant le bouton `Archiver`{.action}. 
 
@@ -106,7 +106,7 @@ C’est pourquoi le SLA est à 48h bien qu'en réalité le délai peut parfois 
 
 Oui, vous pouvez utiliser la classe de stockage Cold Archive pour archiver vos données sauvegardées chez un autre cloud provider.
 
-Par exemple, vous installez un serveur, vous paramétrez Rclone pour synchroniser vos fichiers d'un Object Storage S3 (cloud provider tiers) vers OVHcloud S3 Object Storage, en suivant le guide : [Object Storage - Utiliser S3 Object Storage avec Rclone](/pages/storage_and_backup/object_storage/s3_rclone).
+Par exemple, vous installez un serveur, vous paramétrez Rclone pour synchroniser vos fichiers d'un Object Storage (cloud provider tiers) vers OVHcloud Object Storage, en suivant le guide : [Object Storage - Utiliser Object Storage avec Rclone](/pages/storage_and_backup/object_storage/s3_rclone).
 
 ### Comment télécharger de larges volumes ?
 
@@ -128,7 +128,7 @@ Nous n'offrons pas ce service. Les archives sont conservées dans des cassettes
 
 La facturation se fait au volume en Go par heure.
 
-Pendant la phase de téléchargement, vos volumes de stockage sont facturés au prix de la classe de stockage **Standard object storage - S3 API**.
+Pendant la phase de téléchargement, vos volumes de stockage sont facturés au prix de la classe de stockage **Object Storage - Standard**.
 
 Après archivage du conteneur (*put-archive*), vos volumes de données sont facturés au prix de la classe de stockage **Cold Archive**.
 
@@ -193,7 +193,7 @@ OVHcloud offre un service managé. OVHcloud se charge du remplacement des bandes
 
 ### Puis-je protéger mes données en transit ?
 
-Pour protéger les données contre un vol, la connexion entre un object storage S3 « *from* » et l'object storage OVHcloud « *to* » est chiffrée, protégée par https.
+Pour protéger les données contre un vol, la connexion entre un service Object Storage d'un fournisseur tiers « *from* » et l'Object Storage d'OVHcloud « *to* » est chiffrée, protégée par https.
 
 En complément, nous vous recommandons de chiffrer vos données avant de les envoyer.
 
@@ -210,15 +210,15 @@ Vous avez à votre disposition 4 niveaux d'identifiants :
 - L'utilisateur administrateur (communément appelé *NIC admin*) 
 - L'utilisateur de facturation (communément appelé *NIC billing*)
 - L'utilisateur OpenStack
-- Un utilisateur S3
+- Un utilisateur Object
 
 | ID | Rôle |
 | --- | --- |
 | NIC admin | Administrator<br>Billing |
 | NIC billing | Billing |
 | NIC technical | Administrator |
 | OpenStack user | (1) Administrator<br>(2) Object Storage |
-| S3 user (S3 credentials) | 4 rôles<br>(1) Administrator<br>(2) Read only<br>(3) Read<br>(4) Deny<br><br>Seul le rôle administrateur a accès aux actions de tiering (archive, delete, restore) |
+| Object Storage user (Object Storage credentials) | 4 rôles<br>(1) Administrator<br>(2) Read only<br>(3) Read<br>(4) Deny<br><br>Seul le rôle administrateur a accès aux actions de tiering (archive, delete, restore) |
 
 ## Resilience
 
@@ -234,7 +234,7 @@ La redondance de la donnée est effectuée par un mécanisme d'Erasure Coding 8+
 
 Le SLA du service est disponible sur [cette page](/links/terms-conditions-contracts).
 
-Il correspond à la disponibilité du service Object Storage (endpoint RBX-archive) à 99,9% et des fonctions associées (API S3 et tiering).
+Il correspond à la disponibilité du service Object Storage (endpoint RBX-archive) à 99,9% et des fonctions associées (API compatible S3 et tiering).
 
 ## Aller plus loin
 

Diff for: pages/storage_and_backup/object_storage/cold_archive_getting_started/guide.de-de.md

@@ -42,7 +42,7 @@ delete-ovh-archive = s3api delete-bucket-intelligent-tiering-configuration --id
 
 > [!primary]
 >
-> - `Id` is a string used to identify the S3 Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
+> - `Id` is a string used to identify the S3 **\*** Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
 >
 > - `Status` and `Days` are mandatory but not used.
 >

Diff for: pages/storage_and_backup/object_storage/cold_archive_getting_started/guide.en-asia.md

@@ -42,7 +42,7 @@ delete-ovh-archive = s3api delete-bucket-intelligent-tiering-configuration --id
 
 > [!primary]
 >
-> - `Id` is a string used to identify the S3 Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
+> - `Id` is a string used to identify the S3 **\*** Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
 >
 > - `Status` and `Days` are mandatory but not used.
 >

Diff for: pages/storage_and_backup/object_storage/cold_archive_getting_started/guide.en-au.md

@@ -42,7 +42,7 @@ delete-ovh-archive = s3api delete-bucket-intelligent-tiering-configuration --id
 
 > [!primary]
 >
-> - `Id` is a string used to identify the S3 Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
+> - `Id` is a string used to identify the S3 **\*** Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
 >
 > - `Status` and `Days` are mandatory but not used.
 >

Diff for: pages/storage_and_backup/object_storage/cold_archive_getting_started/guide.en-ca.md

@@ -42,7 +42,7 @@ delete-ovh-archive = s3api delete-bucket-intelligent-tiering-configuration --id
 
 > [!primary]
 >
-> - `Id` is a string used to identify the S3 Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
+> - `Id` is a string used to identify the S3 **\*** Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
 >
 > - `Status` and `Days` are mandatory but not used.
 >

Diff for: pages/storage_and_backup/object_storage/cold_archive_getting_started/guide.en-gb.md

@@ -42,7 +42,7 @@ delete-ovh-archive = s3api delete-bucket-intelligent-tiering-configuration --id
 
 > [!primary]
 >
-> - `Id` is a string used to identify the S3 Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
+> - `Id` is a string used to identify the S3 **\*** Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
 >
 > - `Status` and `Days` are mandatory but not used.
 >

Diff for: pages/storage_and_backup/object_storage/cold_archive_getting_started/guide.en-ie.md

@@ -42,7 +42,7 @@ delete-ovh-archive = s3api delete-bucket-intelligent-tiering-configuration --id
 
 > [!primary]
 >
-> - `Id` is a string used to identify the S3 Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
+> - `Id` is a string used to identify the S3 **\*** Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
 >
 > - `Status` and `Days` are mandatory but not used.
 >

Diff for: pages/storage_and_backup/object_storage/cold_archive_getting_started/guide.en-sg.md

@@ -42,7 +42,7 @@ delete-ovh-archive = s3api delete-bucket-intelligent-tiering-configuration --id
 
 > [!primary]
 >
-> - `Id` is a string used to identify the S3 Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
+> - `Id` is a string used to identify the S3 **\*** Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
 >
 > - `Status` and `Days` are mandatory but not used.
 >

Diff for: pages/storage_and_backup/object_storage/cold_archive_getting_started/guide.en-us.md

@@ -42,7 +42,7 @@ delete-ovh-archive = s3api delete-bucket-intelligent-tiering-configuration --id
 
 > [!primary]
 >
-> - `Id` is a string used to identify the S3 Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
+> - `Id` is a string used to identify the S3 **\*** Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
 >
 > - `Status` and `Days` are mandatory but not used.
 >

Diff for: pages/storage_and_backup/object_storage/cold_archive_getting_started/guide.es-es.md

@@ -42,7 +42,7 @@ delete-ovh-archive = s3api delete-bucket-intelligent-tiering-configuration --id
 
 > [!primary]
 >
-> - `Id` is a string used to identify the S3 Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
+> - `Id` is a string used to identify the S3 **\*** Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
 >
 > - `Status` and `Days` are mandatory but not used.
 >

Diff for: pages/storage_and_backup/object_storage/cold_archive_getting_started/guide.es-us.md

@@ -42,7 +42,7 @@ delete-ovh-archive = s3api delete-bucket-intelligent-tiering-configuration --id
 
 > [!primary]
 >
-> - `Id` is a string used to identify the S3 Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
+> - `Id` is a string used to identify the S3 **\*** Intelligent-Tiering configuration. Its value is arbitrary and up to you. It will be necessary for further PUT, GET and DELETE operations on the intelligent-tiering configuration.
 >
 > - `Status` and `Days` are mandatory but not used.
 >

Diff for: pages/storage_and_backup/object_storage/cold_archive_getting_started/guide.fr-ca.md

@@ -42,7 +42,7 @@ delete-ovh-archive = s3api delete-bucket-intelligent-tiering-configuration --id
 
 > [!primary]
 >
-> - `Id` est une chaîne utilisée pour identifier la configuration de l'Intelligent-Tiering S3. Sa valeur est arbitraire et vous pouvez la modifier. Elle sera nécessaire pour les opérations ultérieures PUT, GET et DELETE sur la configuration de l'Intelligent-Tiering.
+> - `Id` est une chaîne utilisée pour identifier la configuration de l'Intelligent-Tiering S3 **\***. Sa valeur est arbitraire et vous pouvez la modifier. Elle sera nécessaire pour les opérations ultérieures PUT, GET et DELETE sur la configuration de l'Intelligent-Tiering.
 > 
 > - `Status` et `Days` sont obligatoires mais non utilisés.
 >

Diff for: pages/storage_and_backup/object_storage/cold_archive_getting_started/guide.fr-fr.md

@@ -42,7 +42,7 @@ delete-ovh-archive = s3api delete-bucket-intelligent-tiering-configuration --id
 
 > [!primary]
 >
-> - `Id` est une chaîne utilisée pour identifier la configuration de l'Intelligent-Tiering S3. Sa valeur est arbitraire et vous pouvez la modifier. Elle sera nécessaire pour les opérations ultérieures PUT, GET et DELETE sur la configuration de l'Intelligent-Tiering.
+> - `Id` est une chaîne utilisée pour identifier la configuration de l'Intelligent-Tiering S3 **\***. Sa valeur est arbitraire et vous pouvez la modifier. Elle sera nécessaire pour les opérations ultérieures PUT, GET et DELETE sur la configuration de l'Intelligent-Tiering.
 > 
 > - `Status` et `Days` sont obligatoires mais non utilisés.
 >