Skip to content

Object Storage - Update endpoint mapping #7841

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
May 12, 2025
Merged

Object Storage - Update endpoint mapping #7841

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
cf37cb4
Update guide.en-ca.md
lason-ovh May 9, 2025
8b016d9
Update guide.fr-ca.md
lason-ovh May 9, 2025
ae392f7
Update guide.en-ca.md
lason-ovh May 9, 2025
3147618
Update guide.fr-ca.md
lason-ovh May 9, 2025
05fbe9b
EN-GB & FR-FR updates + style improvements
Y0Coss May 12, 2025
eacd018
Date update + Duplication
Y0Coss May 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
59 changes: 36 additions & 23 deletions pages/storage_and_backup/object_storage/s3_location/guide.de-de.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Object Storage - Endpunkte und Objektspeicher mit Geo-Verfügbarkeit (EN)
updated: 2024-11-25
updated: 2025-05-12
---

<style>
Expand All @@ -9,7 +9,7 @@ td:nth-of-type(2) {
}
</style>

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 S3<sup>1</sup>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.

## Object Storage

Expand Down Expand Up @@ -137,26 +137,28 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
<table>
<tr>
<th>AWS</th>
<th>OVHcloud mapping before 2024-06-17</th>
<th>OVHcloud mapping from 2024-06-17</th>
<th>OVHcloud current mapping</th>
<th>OVHcloud mapping from 2025-06-17</th>
</tr>
<tr>
<td>EXPRESS_ONEZONE</td>
<td rowspan=9>Standard</td>
<td>High Performance</td>
<td>High Performance</td>
</tr>
<tr>
<td>STANDARD</td>
<td rowspan=8>Standard</td>
<td rowspan=3>Standard</td>
</tr>
<tr>
<td>default*</td>
<td>INTELLIGENT_TIERING</td>
</tr>
<tr>
<td>STANDARD_IA</td>
<td>default<sup>2</sup></td>
</tr>
<tr>
<td>INTELLIGENT_TIERING</td>
<td>STANDARD_IA</td>
<td rowspan=5>Standard Infrequent Access<sup>3</sup></td>
</tr>
<tr>
<td>ONEZONE_IA</td>
Expand All @@ -172,14 +174,15 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
</tr>
</table>

_* 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._
_<sup>2</sup>: 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._
_<sup>3</sup>: 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:

<table>
<tr>
<th>AWS</th>
<th>OVHcloud mapping from 2024-06-17</th>
<th>OVHcloud</th>
</tr>
<tr>
<td>EXPRESS_ONEZONE</td>
Expand All @@ -189,18 +192,21 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the
<td>STANDARD</td>
<td>Standard</td>
</tr>
<tr>
<td>STANDARD_IA</td>
<td>Standard Infrequent Access<sup>3</sup></td>
</tr>
</table>

_<sup>3</sup>: 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.<region>.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`.

Expand All @@ -209,23 +215,24 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
<table>
<tr>
<th>AWS</th>
<th>OVHcloud mapping before 2024-06-17</th>
<th>OVHcloud mapping from 2024-06-17</th>
<th>OVHcloud current mapping</th>
<th>OVHcloud mapping from 2025-06-17</th>
</tr>
<tr>
<td>EXPRESS_ONEZONE</td>
<td rowspan=9>High Performance</td>
<td rowspan=3>High Performance</td>
<td rowspan=3>High Performance</td>
</tr>
<tr>
<td>STANDARD</td>
</tr>
<tr>
<td>default*</td>
<td>default<sup>4</sup></td>
</tr>
<tr>
<td>STANDARD_IA</td>
<td rowspan=6>Standard</td>
<td rowspan=3>Standard</td>
</tr>
<tr>
<td>INTELLIGENT_TIERING</td>
Expand All @@ -235,6 +242,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
</tr>
<tr>
<td>GLACIER_IR</td>
<td rowspan=3>Standard Infrequent Access<sup>3</sup></td>
</tr>
<tr>
<td>GLACIER</td>
Expand All @@ -244,14 +252,15 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
</tr>
</table>

_* 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._
_<sup>3</sup>: The Standard Infrequent Access tier will be available starting from 2025-06-17._
_<sup>4</sup>: 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:

<table>
<tr>
<th>AWS</th>
<th>OVHcloud mapping from 2024-06-10</th>
<th>OVHcloud</th>
</tr>
<tr>
<td>STANDARD</td>
Expand All @@ -261,9 +270,13 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t
<td>STANDARD_IA</td>
<td>Standard</td>
</tr>
<tr>
<td>GLACIER_IR</td>
<td>Standard Infrequent Access<sup>3</sup></td>
</tr>
</table>

![Schema 2](images/perf-mapping-v2.png)
_<sup>3</sup>: The Standard Infrequent Access tier will be available starting from 2025-06-17._

## Object Storage Swift

Expand All @@ -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.
_<sup>1</sup>: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc._
59 changes: 36 additions & 23 deletions pages/storage_and_backup/object_storage/s3_location/guide.en-asia.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Object Storage - Endpoints and Object Storage geoavailability
updated: 2024-11-25
updated: 2025-05-12
---

<style>
Expand All @@ -9,7 +9,7 @@ td:nth-of-type(2) {
}
</style>

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 S3<sup>1</sup>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.

## Object Storage

Expand Down Expand Up @@ -137,26 +137,28 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
<table>
<tr>
<th>AWS</th>
<th>OVHcloud mapping before 2024-06-17</th>
<th>OVHcloud mapping from 2024-06-17</th>
<th>OVHcloud current mapping</th>
<th>OVHcloud mapping from 2025-06-17</th>
</tr>
<tr>
<td>EXPRESS_ONEZONE</td>
<td rowspan=9>Standard</td>
<td>High Performance</td>
<td>High Performance</td>
</tr>
<tr>
<td>STANDARD</td>
<td rowspan=8>Standard</td>
<td rowspan=3>Standard</td>
</tr>
<tr>
<td>default*</td>
<td>INTELLIGENT_TIERING</td>
</tr>
<tr>
<td>STANDARD_IA</td>
<td>default<sup>2</sup></td>
</tr>
<tr>
<td>INTELLIGENT_TIERING</td>
<td>STANDARD_IA</td>
<td rowspan=5>Standard Infrequent Access<sup>3</sup></td>
</tr>
<tr>
<td>ONEZONE_IA</td>
Expand All @@ -172,14 +174,15 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
</tr>
</table>

_* 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._
_<sup>2</sup>: 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._
_<sup>3</sup>: 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:

<table>
<tr>
<th>AWS</th>
<th>OVHcloud mapping from 2024-06-17</th>
<th>OVHcloud</th>
</tr>
<tr>
<td>EXPRESS_ONEZONE</td>
Expand All @@ -189,18 +192,21 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the
<td>STANDARD</td>
<td>Standard</td>
</tr>
<tr>
<td>STANDARD_IA</td>
<td>Standard Infrequent Access<sup>3</sup></td>
</tr>
</table>

_<sup>3</sup>: 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.<region>.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`.

Expand All @@ -209,23 +215,24 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
<table>
<tr>
<th>AWS</th>
<th>OVHcloud mapping before 2024-06-17</th>
<th>OVHcloud mapping from 2024-06-17</th>
<th>OVHcloud current mapping</th>
<th>OVHcloud mapping from 2025-06-17</th>
</tr>
<tr>
<td>EXPRESS_ONEZONE</td>
<td rowspan=9>High Performance</td>
<td rowspan=3>High Performance</td>
<td rowspan=3>High Performance</td>
</tr>
<tr>
<td>STANDARD</td>
</tr>
<tr>
<td>default*</td>
<td>default<sup>4</sup></td>
</tr>
<tr>
<td>STANDARD_IA</td>
<td rowspan=6>Standard</td>
<td rowspan=3>Standard</td>
</tr>
<tr>
<td>INTELLIGENT_TIERING</td>
Expand All @@ -235,6 +242,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
</tr>
<tr>
<td>GLACIER_IR</td>
<td rowspan=3>Standard Infrequent Access<sup>3</sup></td>
</tr>
<tr>
<td>GLACIER</td>
Expand All @@ -244,14 +252,15 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
</tr>
</table>

_* 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._
_<sup>3</sup>: The Standard Infrequent Access tier will be available starting from 2025-06-17._
_<sup>4</sup>: 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:

<table>
<tr>
<th>AWS</th>
<th>OVHcloud mapping from 2024-06-10</th>
<th>OVHcloud</th>
</tr>
<tr>
<td>STANDARD</td>
Expand All @@ -261,9 +270,13 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t
<td>STANDARD_IA</td>
<td>Standard</td>
</tr>
<tr>
<td>GLACIER_IR</td>
<td>Standard Infrequent Access<sup>3</sup></td>
</tr>
</table>

![Schema 2](images/perf-mapping-v2.png)
_<sup>3</sup>: The Standard Infrequent Access tier will be available starting from 2025-06-17._

## Object Storage Swift

Expand All @@ -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.
_<sup>1</sup>: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc._
Loading