diff --git a/pages/storage_and_backup/object_storage/s3_location/guide.de-de.md b/pages/storage_and_backup/object_storage/s3_location/guide.de-de.md index de727a163b0..ebd58609c17 100644 --- a/pages/storage_and_backup/object_storage/s3_location/guide.de-de.md +++ b/pages/storage_and_backup/object_storage/s3_location/guide.de-de.md @@ -1,6 +1,6 @@ --- title: Object Storage - Endpunkte und Objektspeicher mit Geo-Verfügbarkeit (EN) -updated: 2024-11-25 +updated: 2025-05-12 --- -We have designed the Object Storage storage classes to be **compatible with S3 **\*** API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. +We have designed the Object Storage storage classes to be **compatible with S31API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. ## Object Storage @@ -137,26 +137,28 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin - - + + - + + - + - + - + + @@ -172,14 +174,15 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEStandardHigh Performance High Performance
STANDARD StandardStandard
default*INTELLIGENT_TIERING
STANDARD_IAdefault2
INTELLIGENT_TIERINGSTANDARD_IAStandard Infrequent Access3
ONEZONE_IA
-_* The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_2: The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the following: - + @@ -189,18 +192,21 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the + + + +
AWSOVHcloud mapping from 2024-06-17OVHcloud
EXPRESS_ONEZONESTANDARD Standard
STANDARD_IAStandard Infrequent Access3
+_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ + > [!warning] > Unlike AWS, Express One Zone will be treated as a regular storage class by OVHcloud and all features and API operations will be available. -![Schema 1](images/io-mapping-v2.png) +### Endpoint retrocompatibility > [!warning] -> - The storage class will no longer be defined at the bucket creation level, but at individual object upload level. -> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint wherever possible. - -### Endpoint retrocompatibility +> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint whenever possible. Although the **io** endpoint is be the preferred endpoint to access the OVHcloud Object Storage service, the **legacy** endpoint `https://s3..perf.cloud.ovh.net` will still be maintained for retrocompatibility purposes for tools and applications that do not support the latest AWS Express One Zone storage class. This legacy endpoint will also be able to address all buckets and all objects in both Standard and High Performance storage classes and will support all API operations including `listBucket`. @@ -209,23 +215,24 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow - - + + - + - + + @@ -235,6 +242,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow + @@ -244,14 +252,15 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEHigh PerformanceHigh Performance High Performance
STANDARD
default*default4
STANDARD_IA StandardStandard
INTELLIGENT_TIERING
GLACIER_IRStandard Infrequent Access3
GLACIER
-_* The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ +_4: The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is the following: - + @@ -261,9 +270,13 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t + + + +
AWSOVHcloud mapping from 2024-06-10OVHcloud
STANDARDSTANDARD_IA Standard
GLACIER_IRStandard Infrequent Access3
-![Schema 2](images/perf-mapping-v2.png) +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ ## Object Storage Swift @@ -277,4 +290,4 @@ If you need training or technical assistance to implement our solutions, contact Join our [community of users](/links/community). -**\***: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc. +_1: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc._ diff --git a/pages/storage_and_backup/object_storage/s3_location/guide.en-asia.md b/pages/storage_and_backup/object_storage/s3_location/guide.en-asia.md index 7718d0da3f0..d713b256596 100644 --- a/pages/storage_and_backup/object_storage/s3_location/guide.en-asia.md +++ b/pages/storage_and_backup/object_storage/s3_location/guide.en-asia.md @@ -1,6 +1,6 @@ --- title: Object Storage - Endpoints and Object Storage geoavailability -updated: 2024-11-25 +updated: 2025-05-12 --- -We have designed the Object Storage storage classes to be **compatible with S3 **\*** API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. +We have designed the Object Storage storage classes to be **compatible with S31API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. ## Object Storage @@ -137,26 +137,28 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin - - + + - + + - + - + - + + @@ -172,14 +174,15 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEStandardHigh Performance High Performance
STANDARD StandardStandard
default*INTELLIGENT_TIERING
STANDARD_IAdefault2
INTELLIGENT_TIERINGSTANDARD_IAStandard Infrequent Access3
ONEZONE_IA
-_* The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_2: The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the following: - + @@ -189,18 +192,21 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the + + + +
AWSOVHcloud mapping from 2024-06-17OVHcloud
EXPRESS_ONEZONESTANDARD Standard
STANDARD_IAStandard Infrequent Access3
+_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ + > [!warning] > Unlike AWS, Express One Zone will be treated as a regular storage class by OVHcloud and all features and API operations will be available. -![Schema 1](images/io-mapping-v2.png) +### Endpoint retrocompatibility > [!warning] -> - The storage class will no longer be defined at the bucket creation level, but at individual object upload level. -> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint wherever possible. - -### Endpoint retrocompatibility +> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint whenever possible. Although the **io** endpoint is be the preferred endpoint to access the OVHcloud Object Storage service, the **legacy** endpoint `https://s3..perf.cloud.ovh.net` will still be maintained for retrocompatibility purposes for tools and applications that do not support the latest AWS Express One Zone storage class. This legacy endpoint will also be able to address all buckets and all objects in both Standard and High Performance storage classes and will support all API operations including `listBucket`. @@ -209,23 +215,24 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow - - + + - + - + + @@ -235,6 +242,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow + @@ -244,14 +252,15 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEHigh PerformanceHigh Performance High Performance
STANDARD
default*default4
STANDARD_IA StandardStandard
INTELLIGENT_TIERING
GLACIER_IRStandard Infrequent Access3
GLACIER
-_* The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ +_4: The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is the following: - + @@ -261,9 +270,13 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t + + + +
AWSOVHcloud mapping from 2024-06-10OVHcloud
STANDARDSTANDARD_IA Standard
GLACIER_IRStandard Infrequent Access3
-![Schema 2](images/perf-mapping-v2.png) +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ ## Object Storage Swift @@ -277,4 +290,4 @@ If you need training or technical assistance to implement our solutions, contact Join our [community of users](/links/community). -**\***: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc. +_1: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc._ diff --git a/pages/storage_and_backup/object_storage/s3_location/guide.en-au.md b/pages/storage_and_backup/object_storage/s3_location/guide.en-au.md index 7718d0da3f0..d713b256596 100644 --- a/pages/storage_and_backup/object_storage/s3_location/guide.en-au.md +++ b/pages/storage_and_backup/object_storage/s3_location/guide.en-au.md @@ -1,6 +1,6 @@ --- title: Object Storage - Endpoints and Object Storage geoavailability -updated: 2024-11-25 +updated: 2025-05-12 --- -We have designed the Object Storage storage classes to be **compatible with S3 **\*** API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. +We have designed the Object Storage storage classes to be **compatible with S31API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. ## Object Storage @@ -137,26 +137,28 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin - - + + - + + - + - + - + + @@ -172,14 +174,15 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEStandardHigh Performance High Performance
STANDARD StandardStandard
default*INTELLIGENT_TIERING
STANDARD_IAdefault2
INTELLIGENT_TIERINGSTANDARD_IAStandard Infrequent Access3
ONEZONE_IA
-_* The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_2: The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the following: - + @@ -189,18 +192,21 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the + + + +
AWSOVHcloud mapping from 2024-06-17OVHcloud
EXPRESS_ONEZONESTANDARD Standard
STANDARD_IAStandard Infrequent Access3
+_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ + > [!warning] > Unlike AWS, Express One Zone will be treated as a regular storage class by OVHcloud and all features and API operations will be available. -![Schema 1](images/io-mapping-v2.png) +### Endpoint retrocompatibility > [!warning] -> - The storage class will no longer be defined at the bucket creation level, but at individual object upload level. -> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint wherever possible. - -### Endpoint retrocompatibility +> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint whenever possible. Although the **io** endpoint is be the preferred endpoint to access the OVHcloud Object Storage service, the **legacy** endpoint `https://s3..perf.cloud.ovh.net` will still be maintained for retrocompatibility purposes for tools and applications that do not support the latest AWS Express One Zone storage class. This legacy endpoint will also be able to address all buckets and all objects in both Standard and High Performance storage classes and will support all API operations including `listBucket`. @@ -209,23 +215,24 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow - - + + - + - + + @@ -235,6 +242,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow + @@ -244,14 +252,15 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEHigh PerformanceHigh Performance High Performance
STANDARD
default*default4
STANDARD_IA StandardStandard
INTELLIGENT_TIERING
GLACIER_IRStandard Infrequent Access3
GLACIER
-_* The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ +_4: The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is the following: - + @@ -261,9 +270,13 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t + + + +
AWSOVHcloud mapping from 2024-06-10OVHcloud
STANDARDSTANDARD_IA Standard
GLACIER_IRStandard Infrequent Access3
-![Schema 2](images/perf-mapping-v2.png) +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ ## Object Storage Swift @@ -277,4 +290,4 @@ If you need training or technical assistance to implement our solutions, contact Join our [community of users](/links/community). -**\***: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc. +_1: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc._ diff --git a/pages/storage_and_backup/object_storage/s3_location/guide.en-ca.md b/pages/storage_and_backup/object_storage/s3_location/guide.en-ca.md index 7718d0da3f0..d713b256596 100644 --- a/pages/storage_and_backup/object_storage/s3_location/guide.en-ca.md +++ b/pages/storage_and_backup/object_storage/s3_location/guide.en-ca.md @@ -1,6 +1,6 @@ --- title: Object Storage - Endpoints and Object Storage geoavailability -updated: 2024-11-25 +updated: 2025-05-12 --- -We have designed the Object Storage storage classes to be **compatible with S3 **\*** API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. +We have designed the Object Storage storage classes to be **compatible with S31API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. ## Object Storage @@ -137,26 +137,28 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin - - + + - + + - + - + - + + @@ -172,14 +174,15 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEStandardHigh Performance High Performance
STANDARD StandardStandard
default*INTELLIGENT_TIERING
STANDARD_IAdefault2
INTELLIGENT_TIERINGSTANDARD_IAStandard Infrequent Access3
ONEZONE_IA
-_* The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_2: The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the following: - + @@ -189,18 +192,21 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the + + + +
AWSOVHcloud mapping from 2024-06-17OVHcloud
EXPRESS_ONEZONESTANDARD Standard
STANDARD_IAStandard Infrequent Access3
+_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ + > [!warning] > Unlike AWS, Express One Zone will be treated as a regular storage class by OVHcloud and all features and API operations will be available. -![Schema 1](images/io-mapping-v2.png) +### Endpoint retrocompatibility > [!warning] -> - The storage class will no longer be defined at the bucket creation level, but at individual object upload level. -> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint wherever possible. - -### Endpoint retrocompatibility +> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint whenever possible. Although the **io** endpoint is be the preferred endpoint to access the OVHcloud Object Storage service, the **legacy** endpoint `https://s3..perf.cloud.ovh.net` will still be maintained for retrocompatibility purposes for tools and applications that do not support the latest AWS Express One Zone storage class. This legacy endpoint will also be able to address all buckets and all objects in both Standard and High Performance storage classes and will support all API operations including `listBucket`. @@ -209,23 +215,24 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow - - + + - + - + + @@ -235,6 +242,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow + @@ -244,14 +252,15 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEHigh PerformanceHigh Performance High Performance
STANDARD
default*default4
STANDARD_IA StandardStandard
INTELLIGENT_TIERING
GLACIER_IRStandard Infrequent Access3
GLACIER
-_* The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ +_4: The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is the following: - + @@ -261,9 +270,13 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t + + + +
AWSOVHcloud mapping from 2024-06-10OVHcloud
STANDARDSTANDARD_IA Standard
GLACIER_IRStandard Infrequent Access3
-![Schema 2](images/perf-mapping-v2.png) +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ ## Object Storage Swift @@ -277,4 +290,4 @@ If you need training or technical assistance to implement our solutions, contact Join our [community of users](/links/community). -**\***: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc. +_1: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc._ diff --git a/pages/storage_and_backup/object_storage/s3_location/guide.en-gb.md b/pages/storage_and_backup/object_storage/s3_location/guide.en-gb.md index 7718d0da3f0..d713b256596 100644 --- a/pages/storage_and_backup/object_storage/s3_location/guide.en-gb.md +++ b/pages/storage_and_backup/object_storage/s3_location/guide.en-gb.md @@ -1,6 +1,6 @@ --- title: Object Storage - Endpoints and Object Storage geoavailability -updated: 2024-11-25 +updated: 2025-05-12 --- -We have designed the Object Storage storage classes to be **compatible with S3 **\*** API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. +We have designed the Object Storage storage classes to be **compatible with S31API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. ## Object Storage @@ -137,26 +137,28 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin - - + + - + + - + - + - + + @@ -172,14 +174,15 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEStandardHigh Performance High Performance
STANDARD StandardStandard
default*INTELLIGENT_TIERING
STANDARD_IAdefault2
INTELLIGENT_TIERINGSTANDARD_IAStandard Infrequent Access3
ONEZONE_IA
-_* The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_2: The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the following: - + @@ -189,18 +192,21 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the + + + +
AWSOVHcloud mapping from 2024-06-17OVHcloud
EXPRESS_ONEZONESTANDARD Standard
STANDARD_IAStandard Infrequent Access3
+_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ + > [!warning] > Unlike AWS, Express One Zone will be treated as a regular storage class by OVHcloud and all features and API operations will be available. -![Schema 1](images/io-mapping-v2.png) +### Endpoint retrocompatibility > [!warning] -> - The storage class will no longer be defined at the bucket creation level, but at individual object upload level. -> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint wherever possible. - -### Endpoint retrocompatibility +> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint whenever possible. Although the **io** endpoint is be the preferred endpoint to access the OVHcloud Object Storage service, the **legacy** endpoint `https://s3..perf.cloud.ovh.net` will still be maintained for retrocompatibility purposes for tools and applications that do not support the latest AWS Express One Zone storage class. This legacy endpoint will also be able to address all buckets and all objects in both Standard and High Performance storage classes and will support all API operations including `listBucket`. @@ -209,23 +215,24 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow - - + + - + - + + @@ -235,6 +242,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow + @@ -244,14 +252,15 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEHigh PerformanceHigh Performance High Performance
STANDARD
default*default4
STANDARD_IA StandardStandard
INTELLIGENT_TIERING
GLACIER_IRStandard Infrequent Access3
GLACIER
-_* The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ +_4: The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is the following: - + @@ -261,9 +270,13 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t + + + +
AWSOVHcloud mapping from 2024-06-10OVHcloud
STANDARDSTANDARD_IA Standard
GLACIER_IRStandard Infrequent Access3
-![Schema 2](images/perf-mapping-v2.png) +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ ## Object Storage Swift @@ -277,4 +290,4 @@ If you need training or technical assistance to implement our solutions, contact Join our [community of users](/links/community). -**\***: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc. +_1: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc._ diff --git a/pages/storage_and_backup/object_storage/s3_location/guide.en-ie.md b/pages/storage_and_backup/object_storage/s3_location/guide.en-ie.md index 7718d0da3f0..d713b256596 100644 --- a/pages/storage_and_backup/object_storage/s3_location/guide.en-ie.md +++ b/pages/storage_and_backup/object_storage/s3_location/guide.en-ie.md @@ -1,6 +1,6 @@ --- title: Object Storage - Endpoints and Object Storage geoavailability -updated: 2024-11-25 +updated: 2025-05-12 --- -We have designed the Object Storage storage classes to be **compatible with S3 **\*** API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. +We have designed the Object Storage storage classes to be **compatible with S31API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. ## Object Storage @@ -137,26 +137,28 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin - - + + - + + - + - + - + + @@ -172,14 +174,15 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEStandardHigh Performance High Performance
STANDARD StandardStandard
default*INTELLIGENT_TIERING
STANDARD_IAdefault2
INTELLIGENT_TIERINGSTANDARD_IAStandard Infrequent Access3
ONEZONE_IA
-_* The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_2: The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the following: - + @@ -189,18 +192,21 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the + + + +
AWSOVHcloud mapping from 2024-06-17OVHcloud
EXPRESS_ONEZONESTANDARD Standard
STANDARD_IAStandard Infrequent Access3
+_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ + > [!warning] > Unlike AWS, Express One Zone will be treated as a regular storage class by OVHcloud and all features and API operations will be available. -![Schema 1](images/io-mapping-v2.png) +### Endpoint retrocompatibility > [!warning] -> - The storage class will no longer be defined at the bucket creation level, but at individual object upload level. -> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint wherever possible. - -### Endpoint retrocompatibility +> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint whenever possible. Although the **io** endpoint is be the preferred endpoint to access the OVHcloud Object Storage service, the **legacy** endpoint `https://s3..perf.cloud.ovh.net` will still be maintained for retrocompatibility purposes for tools and applications that do not support the latest AWS Express One Zone storage class. This legacy endpoint will also be able to address all buckets and all objects in both Standard and High Performance storage classes and will support all API operations including `listBucket`. @@ -209,23 +215,24 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow - - + + - + - + + @@ -235,6 +242,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow + @@ -244,14 +252,15 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEHigh PerformanceHigh Performance High Performance
STANDARD
default*default4
STANDARD_IA StandardStandard
INTELLIGENT_TIERING
GLACIER_IRStandard Infrequent Access3
GLACIER
-_* The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ +_4: The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is the following: - + @@ -261,9 +270,13 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t + + + +
AWSOVHcloud mapping from 2024-06-10OVHcloud
STANDARDSTANDARD_IA Standard
GLACIER_IRStandard Infrequent Access3
-![Schema 2](images/perf-mapping-v2.png) +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ ## Object Storage Swift @@ -277,4 +290,4 @@ If you need training or technical assistance to implement our solutions, contact Join our [community of users](/links/community). -**\***: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc. +_1: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc._ diff --git a/pages/storage_and_backup/object_storage/s3_location/guide.en-sg.md b/pages/storage_and_backup/object_storage/s3_location/guide.en-sg.md index 7718d0da3f0..d713b256596 100644 --- a/pages/storage_and_backup/object_storage/s3_location/guide.en-sg.md +++ b/pages/storage_and_backup/object_storage/s3_location/guide.en-sg.md @@ -1,6 +1,6 @@ --- title: Object Storage - Endpoints and Object Storage geoavailability -updated: 2024-11-25 +updated: 2025-05-12 --- -We have designed the Object Storage storage classes to be **compatible with S3 **\*** API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. +We have designed the Object Storage storage classes to be **compatible with S31API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. ## Object Storage @@ -137,26 +137,28 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin - - + + - + + - + - + - + + @@ -172,14 +174,15 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEStandardHigh Performance High Performance
STANDARD StandardStandard
default*INTELLIGENT_TIERING
STANDARD_IAdefault2
INTELLIGENT_TIERINGSTANDARD_IAStandard Infrequent Access3
ONEZONE_IA
-_* The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_2: The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the following: - + @@ -189,18 +192,21 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the + + + +
AWSOVHcloud mapping from 2024-06-17OVHcloud
EXPRESS_ONEZONESTANDARD Standard
STANDARD_IAStandard Infrequent Access3
+_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ + > [!warning] > Unlike AWS, Express One Zone will be treated as a regular storage class by OVHcloud and all features and API operations will be available. -![Schema 1](images/io-mapping-v2.png) +### Endpoint retrocompatibility > [!warning] -> - The storage class will no longer be defined at the bucket creation level, but at individual object upload level. -> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint wherever possible. - -### Endpoint retrocompatibility +> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint whenever possible. Although the **io** endpoint is be the preferred endpoint to access the OVHcloud Object Storage service, the **legacy** endpoint `https://s3..perf.cloud.ovh.net` will still be maintained for retrocompatibility purposes for tools and applications that do not support the latest AWS Express One Zone storage class. This legacy endpoint will also be able to address all buckets and all objects in both Standard and High Performance storage classes and will support all API operations including `listBucket`. @@ -209,23 +215,24 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow - - + + - + - + + @@ -235,6 +242,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow + @@ -244,14 +252,15 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEHigh PerformanceHigh Performance High Performance
STANDARD
default*default4
STANDARD_IA StandardStandard
INTELLIGENT_TIERING
GLACIER_IRStandard Infrequent Access3
GLACIER
-_* The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ +_4: The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is the following: - + @@ -261,9 +270,13 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t + + + +
AWSOVHcloud mapping from 2024-06-10OVHcloud
STANDARDSTANDARD_IA Standard
GLACIER_IRStandard Infrequent Access3
-![Schema 2](images/perf-mapping-v2.png) +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ ## Object Storage Swift @@ -277,4 +290,4 @@ If you need training or technical assistance to implement our solutions, contact Join our [community of users](/links/community). -**\***: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc. +_1: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc._ diff --git a/pages/storage_and_backup/object_storage/s3_location/guide.en-us.md b/pages/storage_and_backup/object_storage/s3_location/guide.en-us.md index 7718d0da3f0..d713b256596 100644 --- a/pages/storage_and_backup/object_storage/s3_location/guide.en-us.md +++ b/pages/storage_and_backup/object_storage/s3_location/guide.en-us.md @@ -1,6 +1,6 @@ --- title: Object Storage - Endpoints and Object Storage geoavailability -updated: 2024-11-25 +updated: 2025-05-12 --- -We have designed the Object Storage storage classes to be **compatible with S3 **\*** API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. +We have designed the Object Storage storage classes to be **compatible with S31API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. ## Object Storage @@ -137,26 +137,28 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin - - + + - + + - + - + - + + @@ -172,14 +174,15 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEStandardHigh Performance High Performance
STANDARD StandardStandard
default*INTELLIGENT_TIERING
STANDARD_IAdefault2
INTELLIGENT_TIERINGSTANDARD_IAStandard Infrequent Access3
ONEZONE_IA
-_* The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_2: The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the following: - + @@ -189,18 +192,21 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the + + + +
AWSOVHcloud mapping from 2024-06-17OVHcloud
EXPRESS_ONEZONESTANDARD Standard
STANDARD_IAStandard Infrequent Access3
+_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ + > [!warning] > Unlike AWS, Express One Zone will be treated as a regular storage class by OVHcloud and all features and API operations will be available. -![Schema 1](images/io-mapping-v2.png) +### Endpoint retrocompatibility > [!warning] -> - The storage class will no longer be defined at the bucket creation level, but at individual object upload level. -> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint wherever possible. - -### Endpoint retrocompatibility +> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint whenever possible. Although the **io** endpoint is be the preferred endpoint to access the OVHcloud Object Storage service, the **legacy** endpoint `https://s3..perf.cloud.ovh.net` will still be maintained for retrocompatibility purposes for tools and applications that do not support the latest AWS Express One Zone storage class. This legacy endpoint will also be able to address all buckets and all objects in both Standard and High Performance storage classes and will support all API operations including `listBucket`. @@ -209,23 +215,24 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow - - + + - + - + + @@ -235,6 +242,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow + @@ -244,14 +252,15 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEHigh PerformanceHigh Performance High Performance
STANDARD
default*default4
STANDARD_IA StandardStandard
INTELLIGENT_TIERING
GLACIER_IRStandard Infrequent Access3
GLACIER
-_* The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ +_4: The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is the following: - + @@ -261,9 +270,13 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t + + + +
AWSOVHcloud mapping from 2024-06-10OVHcloud
STANDARDSTANDARD_IA Standard
GLACIER_IRStandard Infrequent Access3
-![Schema 2](images/perf-mapping-v2.png) +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ ## Object Storage Swift @@ -277,4 +290,4 @@ If you need training or technical assistance to implement our solutions, contact Join our [community of users](/links/community). -**\***: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc. +_1: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc._ diff --git a/pages/storage_and_backup/object_storage/s3_location/guide.es-es.md b/pages/storage_and_backup/object_storage/s3_location/guide.es-es.md index a560f499b8e..995c2eb6066 100644 --- a/pages/storage_and_backup/object_storage/s3_location/guide.es-es.md +++ b/pages/storage_and_backup/object_storage/s3_location/guide.es-es.md @@ -1,6 +1,6 @@ --- title: Object Storage - Endpoints y geodisponibilidad del Object Storage (EN) -updated: 2024-11-25 +updated: 2025-05-12 --- -We have designed the Object Storage storage classes to be **compatible with S3 **\*** API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. +We have designed the Object Storage storage classes to be **compatible with S31API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. ## Object Storage @@ -137,26 +137,28 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin - - + + - + + - + - + - + + @@ -172,14 +174,15 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEStandardHigh Performance High Performance
STANDARD StandardStandard
default*INTELLIGENT_TIERING
STANDARD_IAdefault2
INTELLIGENT_TIERINGSTANDARD_IAStandard Infrequent Access3
ONEZONE_IA
-_* The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_2: The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the following: - + @@ -189,18 +192,21 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the + + + +
AWSOVHcloud mapping from 2024-06-17OVHcloud
EXPRESS_ONEZONESTANDARD Standard
STANDARD_IAStandard Infrequent Access3
+_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ + > [!warning] > Unlike AWS, Express One Zone will be treated as a regular storage class by OVHcloud and all features and API operations will be available. -![Schema 1](images/io-mapping-v2.png) +### Endpoint retrocompatibility > [!warning] -> - The storage class will no longer be defined at the bucket creation level, but at individual object upload level. -> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint wherever possible. - -### Endpoint retrocompatibility +> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint whenever possible. Although the **io** endpoint is be the preferred endpoint to access the OVHcloud Object Storage service, the **legacy** endpoint `https://s3..perf.cloud.ovh.net` will still be maintained for retrocompatibility purposes for tools and applications that do not support the latest AWS Express One Zone storage class. This legacy endpoint will also be able to address all buckets and all objects in both Standard and High Performance storage classes and will support all API operations including `listBucket`. @@ -209,23 +215,24 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow - - + + - + - + + @@ -235,6 +242,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow + @@ -244,14 +252,15 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEHigh PerformanceHigh Performance High Performance
STANDARD
default*default4
STANDARD_IA StandardStandard
INTELLIGENT_TIERING
GLACIER_IRStandard Infrequent Access3
GLACIER
-_* The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ +_4: The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is the following: - + @@ -261,9 +270,13 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t + + + +
AWSOVHcloud mapping from 2024-06-10OVHcloud
STANDARDSTANDARD_IA Standard
GLACIER_IRStandard Infrequent Access3
-![Schema 2](images/perf-mapping-v2.png) +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ ## Object Storage Swift @@ -277,4 +290,4 @@ If you need training or technical assistance to implement our solutions, contact Join our [community of users](/links/community). -**\***: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc. +_1: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc._ diff --git a/pages/storage_and_backup/object_storage/s3_location/guide.es-us.md b/pages/storage_and_backup/object_storage/s3_location/guide.es-us.md index a560f499b8e..995c2eb6066 100644 --- a/pages/storage_and_backup/object_storage/s3_location/guide.es-us.md +++ b/pages/storage_and_backup/object_storage/s3_location/guide.es-us.md @@ -1,6 +1,6 @@ --- title: Object Storage - Endpoints y geodisponibilidad del Object Storage (EN) -updated: 2024-11-25 +updated: 2025-05-12 --- -We have designed the Object Storage storage classes to be **compatible with S3 **\*** API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. +We have designed the Object Storage storage classes to be **compatible with S31API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. ## Object Storage @@ -137,26 +137,28 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin - - + + - + + - + - + - + + @@ -172,14 +174,15 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEStandardHigh Performance High Performance
STANDARD StandardStandard
default*INTELLIGENT_TIERING
STANDARD_IAdefault2
INTELLIGENT_TIERINGSTANDARD_IAStandard Infrequent Access3
ONEZONE_IA
-_* The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_2: The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the following: - + @@ -189,18 +192,21 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the + + + +
AWSOVHcloud mapping from 2024-06-17OVHcloud
EXPRESS_ONEZONESTANDARD Standard
STANDARD_IAStandard Infrequent Access3
+_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ + > [!warning] > Unlike AWS, Express One Zone will be treated as a regular storage class by OVHcloud and all features and API operations will be available. -![Schema 1](images/io-mapping-v2.png) +### Endpoint retrocompatibility > [!warning] -> - The storage class will no longer be defined at the bucket creation level, but at individual object upload level. -> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint wherever possible. - -### Endpoint retrocompatibility +> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint whenever possible. Although the **io** endpoint is be the preferred endpoint to access the OVHcloud Object Storage service, the **legacy** endpoint `https://s3..perf.cloud.ovh.net` will still be maintained for retrocompatibility purposes for tools and applications that do not support the latest AWS Express One Zone storage class. This legacy endpoint will also be able to address all buckets and all objects in both Standard and High Performance storage classes and will support all API operations including `listBucket`. @@ -209,23 +215,24 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow - - + + - + - + + @@ -235,6 +242,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow + @@ -244,14 +252,15 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEHigh PerformanceHigh Performance High Performance
STANDARD
default*default4
STANDARD_IA StandardStandard
INTELLIGENT_TIERING
GLACIER_IRStandard Infrequent Access3
GLACIER
-_* The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ +_4: The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is the following: - + @@ -261,9 +270,13 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t + + + +
AWSOVHcloud mapping from 2024-06-10OVHcloud
STANDARDSTANDARD_IA Standard
GLACIER_IRStandard Infrequent Access3
-![Schema 2](images/perf-mapping-v2.png) +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ ## Object Storage Swift @@ -277,4 +290,4 @@ If you need training or technical assistance to implement our solutions, contact Join our [community of users](/links/community). -**\***: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc. +_1: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc._ diff --git a/pages/storage_and_backup/object_storage/s3_location/guide.fr-ca.md b/pages/storage_and_backup/object_storage/s3_location/guide.fr-ca.md index 7d16d984799..97d9ef3e24b 100644 --- a/pages/storage_and_backup/object_storage/s3_location/guide.fr-ca.md +++ b/pages/storage_and_backup/object_storage/s3_location/guide.fr-ca.md @@ -1,6 +1,6 @@ --- title: Object Storage - Endpoints et géo-disponibilité de l’Object Storage -updated: 2024-11-25 +updated: 2025-05-12 --- -Nous avons conçu les classes de stockage Object Storage pour qu’elles soient **compatibles avec S3 \***, considérée comme une référence sur le marché du stockage objet. Vous pouvez donc utiliser l'Object Storage avec la plupart des outils de gestion de données via les points de terminaison définis par région et non par classe de stockage. +Nous avons conçu les classes de stockage Object Storage pour qu’elles soient **compatibles avec S31 AWS - Mapping OVHcloud avant le 17/06/2024 - Mapping OVHcloud à partir du 17/06/2024 + OVHcloud mapping actuel + OVHcloud mapping à partir du 17-06-2025 EXPRESS_ONEZONE - Standard + High Performance High Performance STANDARD Standard + Standard - Par défaut * + INTELLIGENT_TIERING - STANDARD_IA + defaut2 - INTELLIGENT_TIERING + STANDARD_IA + Standard Infrequent Access3 ONEZONE_IA @@ -172,14 +174,15 @@ Le mapping des opérations **WRITE(PUT)** sur le point de terminaison **io** est -_* La classe de stockage par défaut sur le point de terminaison **io** sera Standard, c'est-à-dire que si vous ne spécifiez pas de classe de stockage, votre objet sera stocké dans notre niveau Standard._ +_2 :La classe de stockage par défaut sur le point de terminaison **io** sera Standard, c'est-à-dire que si vous ne spécifiez pas de classe de stockage, votre objet sera stocké dans notre niveau Standard._ +_3 : Le niveau de stockage Standard Infrequent Access sera disponible à partir du 17-06-2025._ Le mapping des opérations **READ(GET/LIST/HEAD)** sur le point de terminaison **io** est le suivant : - + @@ -189,19 +192,22 @@ Le mapping des opérations **READ(GET/LIST/HEAD)** sur le point de terminaison * + + + +
AWSMapping OVHcloud à partir du 17/06/2024OVHcloud
EXPRESS_ONEZONESTANDARD Standard
STANDARD_IAStandard Infrequent Access3
+_3 : Le niveau de stockage Standard Infrequent Access sera disponible à partir du 17-06-2025._ + > [!warning] > Contrairement à AWS, Express One Zone sera traité comme une classe de stockage régulière par OVHcloud et toutes les fonctionnalités et opérations d'API seront disponibles. -![Schema 1](images/io-mapping-v2.png) +### Rétrocompatibilité des points de terminaison > [!warning] -> - La classe de stockage ne sera plus définie au niveau de la création du bucket, mais au niveau de l'upload d'objets individuels. > - Le point de terminaison **perf** sera maintenu à des fins de rétrocompatibilité uniquement, afin de permettre aux outils qui ne prennent pas en charge la récente classe de stockage Express_One_Zone d'AWS de continuer à fonctionner sur notre object storage. Nous vous encourageons donc fortement à migrer vers le point de terminaison **io** cible chaque fois que cela est possible. -### Rétrocompatibilité des points de terminaison - Bien que le point de terminaison **io** soit le point de terminaison préféré pour accéder au service OVHcloud Object Storage, le point de terminaison **historique** `https://s3..perf.cloud.ovh.net` sera toujours maintenu à des fins de rétrocompatibilité pour les outils et les applications qui ne prennent pas en charge la dernière classe de stockage AWS Express One Zone. Ce point de terminaison historique sera également en mesure de prendre en charge tous les buckets et tous les objets dans les classes de stockage Standard et High Performance et prendra en charge toutes les opérations, y compris `listBucket`. Le mapping des opérations **WRITE(PUT)** sur le point de terminaison **perf** est le suivant : @@ -209,23 +215,24 @@ Le mapping des opérations **WRITE(PUT)** sur le point de terminaison **perf** e - - + + - + - + + @@ -235,6 +242,7 @@ Le mapping des opérations **WRITE(PUT)** sur le point de terminaison **perf** e + @@ -244,14 +252,14 @@ Le mapping des opérations **WRITE(PUT)** sur le point de terminaison **perf** e
AWSMapping OVHcloud avant le 17/06/2024Mapping OVHcloud à partir du 17/06/2024OVHcloud mapping actuelOVHcloud mapping à partir du 17-06-2025
EXPRESS_ONEZONEHigh PerformanceHigh Performance High Performance
STANDARD
Par défaut *default4
STANDARD_IA StandardStandard
INTELLIGENT_TIERING
GLACIER_IRStandard Infrequent Access3
GLACIER
-_* Le niveau de stockage par défaut sur le point de terminaison **perf** sera High Performance, c'est-à-dire que si vous ne spécifiez pas de classe de stockage, votre objet sera stocké dans notre niveau High Performance._ +_3 : Le niveau de stockage Standard Infrequent Access sera disponible à partir du 17-06-2025._ +_4 : Le niveau de stockage par défaut sur le point de terminaison **perf** sera High Performance, c'est-à-dire que si vous ne spécifiez pas de classe de stockage, votre objet sera stocké dans notre niveau High Performance._ Le mapping des opérations **READ(GET/LIST/HEAD)** sur le point de terminaison **perf** est le suivant : - - + @@ -261,9 +269,13 @@ Le mapping des opérations **READ(GET/LIST/HEAD)** sur le point de terminaison * + + + +
AWSMapping OVHcloud à partir du 10/06/2024OVHcloud
STANDARDSTANDARD_IA Standard
GLACIER_IRStandard Infrequent Access3
-![Schema 2](images/perf-mapping-v2.png) +_3 : Le niveau de stockage Standard Infrequent Access sera disponible à partir du 17-06-2025._ ## Object Storage Swift @@ -277,4 +289,4 @@ Si vous avez besoin d'une formation ou d'une assistance technique pour la mise e Échangez avec notre [communauté d'utilisateurs](/links/community). -**\*** : S3 est une marque déposée appartenant à Amazon Technologies, Inc. Les services de OVHcloud ne sont pas sponsorisés, approuvés, ou affiliés de quelque manière que ce soit. +_1 @@ -9,7 +9,7 @@ td:nth-of-type(2) { } -Nous avons conçu les classes de stockage Object Storage pour qu’elles soient **compatibles avec S3 \***, considérée comme une référence sur le marché du stockage objet. Vous pouvez donc utiliser l'Object Storage avec la plupart des outils de gestion de données via les points de terminaison définis par région et non par classe de stockage. +Nous avons conçu les classes de stockage Object Storage pour qu’elles soient **compatibles avec S31 AWS - Mapping OVHcloud avant le 17/06/2024 - Mapping OVHcloud à partir du 17/06/2024 + OVHcloud mapping actuel + OVHcloud mapping à partir du 17-06-2025 EXPRESS_ONEZONE - Standard + High Performance High Performance STANDARD Standard + Standard - Par défaut * + INTELLIGENT_TIERING - STANDARD_IA + defaut2 - INTELLIGENT_TIERING + STANDARD_IA + Standard Infrequent Access3 ONEZONE_IA @@ -172,14 +174,15 @@ Le mapping des opérations **WRITE(PUT)** sur le point de terminaison **io** est -_* La classe de stockage par défaut sur le point de terminaison **io** sera Standard, c'est-à-dire que si vous ne spécifiez pas de classe de stockage, votre objet sera stocké dans notre niveau Standard._ +_2 :La classe de stockage par défaut sur le point de terminaison **io** sera Standard, c'est-à-dire que si vous ne spécifiez pas de classe de stockage, votre objet sera stocké dans notre niveau Standard._ +_3 : Le niveau de stockage Standard Infrequent Access sera disponible à partir du 17-06-2025._ Le mapping des opérations **READ(GET/LIST/HEAD)** sur le point de terminaison **io** est le suivant : - + @@ -189,19 +192,22 @@ Le mapping des opérations **READ(GET/LIST/HEAD)** sur le point de terminaison * + + + +
AWSMapping OVHcloud à partir du 17/06/2024OVHcloud
EXPRESS_ONEZONESTANDARD Standard
STANDARD_IAStandard Infrequent Access3
+_3 : Le niveau de stockage Standard Infrequent Access sera disponible à partir du 17-06-2025._ + > [!warning] > Contrairement à AWS, Express One Zone sera traité comme une classe de stockage régulière par OVHcloud et toutes les fonctionnalités et opérations d'API seront disponibles. -![Schema 1](images/io-mapping-v2.png) +### Rétrocompatibilité des points de terminaison > [!warning] -> - La classe de stockage ne sera plus définie au niveau de la création du bucket, mais au niveau de l'upload d'objets individuels. > - Le point de terminaison **perf** sera maintenu à des fins de rétrocompatibilité uniquement, afin de permettre aux outils qui ne prennent pas en charge la récente classe de stockage Express_One_Zone d'AWS de continuer à fonctionner sur notre object storage. Nous vous encourageons donc fortement à migrer vers le point de terminaison **io** cible chaque fois que cela est possible. -### Rétrocompatibilité des points de terminaison - Bien que le point de terminaison **io** soit le point de terminaison préféré pour accéder au service OVHcloud Object Storage, le point de terminaison **historique** `https://s3..perf.cloud.ovh.net` sera toujours maintenu à des fins de rétrocompatibilité pour les outils et les applications qui ne prennent pas en charge la dernière classe de stockage AWS Express One Zone. Ce point de terminaison historique sera également en mesure de prendre en charge tous les buckets et tous les objets dans les classes de stockage Standard et High Performance et prendra en charge toutes les opérations, y compris `listBucket`. Le mapping des opérations **WRITE(PUT)** sur le point de terminaison **perf** est le suivant : @@ -209,23 +215,24 @@ Le mapping des opérations **WRITE(PUT)** sur le point de terminaison **perf** e - - + + - + - + + @@ -235,6 +242,7 @@ Le mapping des opérations **WRITE(PUT)** sur le point de terminaison **perf** e + @@ -244,14 +252,14 @@ Le mapping des opérations **WRITE(PUT)** sur le point de terminaison **perf** e
AWSMapping OVHcloud avant le 17/06/2024Mapping OVHcloud à partir du 17/06/2024OVHcloud mapping actuelOVHcloud mapping à partir du 17-06-2025
EXPRESS_ONEZONEHigh PerformanceHigh Performance High Performance
STANDARD
Par défaut *default4
STANDARD_IA StandardStandard
INTELLIGENT_TIERING
GLACIER_IRStandard Infrequent Access3
GLACIER
-_* Le niveau de stockage par défaut sur le point de terminaison **perf** sera High Performance, c'est-à-dire que si vous ne spécifiez pas de classe de stockage, votre objet sera stocké dans notre niveau High Performance._ +_3 : Le niveau de stockage Standard Infrequent Access sera disponible à partir du 17-06-2025._ +_4 : Le niveau de stockage par défaut sur le point de terminaison **perf** sera High Performance, c'est-à-dire que si vous ne spécifiez pas de classe de stockage, votre objet sera stocké dans notre niveau High Performance._ Le mapping des opérations **READ(GET/LIST/HEAD)** sur le point de terminaison **perf** est le suivant : - - + @@ -261,9 +269,13 @@ Le mapping des opérations **READ(GET/LIST/HEAD)** sur le point de terminaison * + + + +
AWSMapping OVHcloud à partir du 10/06/2024OVHcloud
STANDARDSTANDARD_IA Standard
GLACIER_IRStandard Infrequent Access3
-![Schema 2](images/perf-mapping-v2.png) +_3 : Le niveau de stockage Standard Infrequent Access sera disponible à partir du 17-06-2025._ ## Object Storage Swift @@ -277,4 +289,4 @@ Si vous avez besoin d'une formation ou d'une assistance technique pour la mise e Échangez avec notre [communauté d'utilisateurs](/links/community). -**\*** : S3 est une marque déposée appartenant à Amazon Technologies, Inc. Les services de OVHcloud ne sont pas sponsorisés, approuvés, ou affiliés de quelque manière que ce soit. \ No newline at end of file +_1 @@ -9,7 +9,7 @@ td:nth-of-type(2) { } -We have designed the Object Storage storage classes to be **compatible with S3 **\*** API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. +We have designed the Object Storage storage classes to be **compatible with S31API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. ## Object Storage @@ -137,26 +137,28 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin - - + + - + + - + - + - + + @@ -172,14 +174,15 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEStandardHigh Performance High Performance
STANDARD StandardStandard
default*INTELLIGENT_TIERING
STANDARD_IAdefault2
INTELLIGENT_TIERINGSTANDARD_IAStandard Infrequent Access3
ONEZONE_IA
-_* The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_2: The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the following: - + @@ -189,18 +192,21 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the + + + +
AWSOVHcloud mapping from 2024-06-17OVHcloud
EXPRESS_ONEZONESTANDARD Standard
STANDARD_IAStandard Infrequent Access3
+_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ + > [!warning] > Unlike AWS, Express One Zone will be treated as a regular storage class by OVHcloud and all features and API operations will be available. -![Schema 1](images/io-mapping-v2.png) +### Endpoint retrocompatibility > [!warning] -> - The storage class will no longer be defined at the bucket creation level, but at individual object upload level. -> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint wherever possible. - -### Endpoint retrocompatibility +> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint whenever possible. Although the **io** endpoint is be the preferred endpoint to access the OVHcloud Object Storage service, the **legacy** endpoint `https://s3..perf.cloud.ovh.net` will still be maintained for retrocompatibility purposes for tools and applications that do not support the latest AWS Express One Zone storage class. This legacy endpoint will also be able to address all buckets and all objects in both Standard and High Performance storage classes and will support all API operations including `listBucket`. @@ -209,23 +215,24 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow - - + + - + - + + @@ -235,6 +242,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow + @@ -244,14 +252,15 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEHigh PerformanceHigh Performance High Performance
STANDARD
default*default4
STANDARD_IA StandardStandard
INTELLIGENT_TIERING
GLACIER_IRStandard Infrequent Access3
GLACIER
-_* The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ +_4: The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is the following: - + @@ -261,9 +270,13 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t + + + +
AWSOVHcloud mapping from 2024-06-10OVHcloud
STANDARDSTANDARD_IA Standard
GLACIER_IRStandard Infrequent Access3
-![Schema 2](images/perf-mapping-v2.png) +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ ## Object Storage Swift @@ -277,4 +290,4 @@ If you need training or technical assistance to implement our solutions, contact Join our [community of users](/links/community). -**\***: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc. +_1: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc._ diff --git a/pages/storage_and_backup/object_storage/s3_location/guide.pl-pl.md b/pages/storage_and_backup/object_storage/s3_location/guide.pl-pl.md index d9b36c7fb87..6152f92690d 100644 --- a/pages/storage_and_backup/object_storage/s3_location/guide.pl-pl.md +++ b/pages/storage_and_backup/object_storage/s3_location/guide.pl-pl.md @@ -1,6 +1,6 @@ --- title: Object Storage - Punkty końcowe i Object Storage geoavailability (EN) -updated: 2024-11-25 +updated: 2025-05-12 --- -We have designed the Object Storage storage classes to be **compatible with S3 **\*** API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. +We have designed the Object Storage storage classes to be **compatible with S31API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. ## Object Storage @@ -137,26 +137,28 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin - - + + - + + - + - + - + + @@ -172,14 +174,15 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEStandardHigh Performance High Performance
STANDARD StandardStandard
default*INTELLIGENT_TIERING
STANDARD_IAdefault2
INTELLIGENT_TIERINGSTANDARD_IAStandard Infrequent Access3
ONEZONE_IA
-_* The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_2: The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the following: - + @@ -189,18 +192,21 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the + + + +
AWSOVHcloud mapping from 2024-06-17OVHcloud
EXPRESS_ONEZONESTANDARD Standard
STANDARD_IAStandard Infrequent Access3
+_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ + > [!warning] > Unlike AWS, Express One Zone will be treated as a regular storage class by OVHcloud and all features and API operations will be available. -![Schema 1](images/io-mapping-v2.png) +### Endpoint retrocompatibility > [!warning] -> - The storage class will no longer be defined at the bucket creation level, but at individual object upload level. -> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint wherever possible. - -### Endpoint retrocompatibility +> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint whenever possible. Although the **io** endpoint is be the preferred endpoint to access the OVHcloud Object Storage service, the **legacy** endpoint `https://s3..perf.cloud.ovh.net` will still be maintained for retrocompatibility purposes for tools and applications that do not support the latest AWS Express One Zone storage class. This legacy endpoint will also be able to address all buckets and all objects in both Standard and High Performance storage classes and will support all API operations including `listBucket`. @@ -209,23 +215,24 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow - - + + - + - + + @@ -235,6 +242,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow + @@ -244,14 +252,15 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEHigh PerformanceHigh Performance High Performance
STANDARD
default*default4
STANDARD_IA StandardStandard
INTELLIGENT_TIERING
GLACIER_IRStandard Infrequent Access3
GLACIER
-_* The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ +_4: The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is the following: - + @@ -261,9 +270,13 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t + + + +
AWSOVHcloud mapping from 2024-06-10OVHcloud
STANDARDSTANDARD_IA Standard
GLACIER_IRStandard Infrequent Access3
-![Schema 2](images/perf-mapping-v2.png) +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ ## Object Storage Swift @@ -277,4 +290,4 @@ If you need training or technical assistance to implement our solutions, contact Join our [community of users](/links/community). -**\***: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc. +_1: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc._ diff --git a/pages/storage_and_backup/object_storage/s3_location/guide.pt-pt.md b/pages/storage_and_backup/object_storage/s3_location/guide.pt-pt.md index 0a45cd767d1..141fba27781 100644 --- a/pages/storage_and_backup/object_storage/s3_location/guide.pt-pt.md +++ b/pages/storage_and_backup/object_storage/s3_location/guide.pt-pt.md @@ -1,6 +1,6 @@ --- title: Object Storage - Endpoints e geoavailability do Object Storage (EN) -updated: 2024-11-25 +updated: 2025-05-12 --- -We have designed the Object Storage storage classes to be **compatible with S3 **\*** API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. +We have designed the Object Storage storage classes to be **compatible with S31API**, considered as a benchmark in the object storage market. You can therefore use Object Storage with most data management tools via the endpoints defined by region and not storage class. ## Object Storage @@ -137,26 +137,28 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin - - + + - + + - + - + - + + @@ -172,14 +174,15 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEStandardHigh Performance High Performance
STANDARD StandardStandard
default*INTELLIGENT_TIERING
STANDARD_IAdefault2
INTELLIGENT_TIERINGSTANDARD_IAStandard Infrequent Access3
ONEZONE_IA
-_* The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_2: The default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class, your object will be stored in our Standard tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the following: - + @@ -189,18 +192,21 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the + + + +
AWSOVHcloud mapping from 2024-06-17OVHcloud
EXPRESS_ONEZONESTANDARD Standard
STANDARD_IAStandard Infrequent Access3
+_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ + > [!warning] > Unlike AWS, Express One Zone will be treated as a regular storage class by OVHcloud and all features and API operations will be available. -![Schema 1](images/io-mapping-v2.png) +### Endpoint retrocompatibility > [!warning] -> - The storage class will no longer be defined at the bucket creation level, but at individual object upload level. -> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint wherever possible. - -### Endpoint retrocompatibility +> - The **perf** endpoint will be maintained for backward compatibility purposes only, to allow tools that don't support AWS's recent Express_One_Zone storage class to continue operating on our object storage thus we strongly encourage you to migrate to the target **io** endpoint whenever possible. Although the **io** endpoint is be the preferred endpoint to access the OVHcloud Object Storage service, the **legacy** endpoint `https://s3..perf.cloud.ovh.net` will still be maintained for retrocompatibility purposes for tools and applications that do not support the latest AWS Express One Zone storage class. This legacy endpoint will also be able to address all buckets and all objects in both Standard and High Performance storage classes and will support all API operations including `listBucket`. @@ -209,23 +215,24 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow - - + + - + - + + @@ -235,6 +242,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow + @@ -244,14 +252,15 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
AWSOVHcloud mapping before 2024-06-17OVHcloud mapping from 2024-06-17OVHcloud current mappingOVHcloud mapping from 2025-06-17
EXPRESS_ONEZONEHigh PerformanceHigh Performance High Performance
STANDARD
default*default4
STANDARD_IA StandardStandard
INTELLIGENT_TIERING
GLACIER_IRStandard Infrequent Access3
GLACIER
-_* The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ +_4: The default storage tier on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class, your object will be stored in our High Performance tier._ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is the following: - + @@ -261,9 +270,13 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t + + + +
AWSOVHcloud mapping from 2024-06-10OVHcloud
STANDARDSTANDARD_IA Standard
GLACIER_IRStandard Infrequent Access3
-![Schema 2](images/perf-mapping-v2.png) +_3: The Standard Infrequent Access tier will be available starting from 2025-06-17._ ## Object Storage Swift @@ -277,4 +290,4 @@ If you need training or technical assistance to implement our solutions, contact Join our [community of users](/links/community). -**\***: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc. +_1: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc._