Skip to content

Object Storage - update endpoints #8474

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 3 commits into from
Oct 3, 2025
Merged

Object Storage - update endpoints #8474

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
770b015
Update guide.en-gb.md
lason-ovh Oct 2, 2025
d86b1c8
Update guide.fr-fr.md
lason-ovh Oct 2, 2025
026e8cb
Proofreading & Duplication
Y0Coss Oct 2, 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
30 changes: 10 additions & 20 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: 2025-06-04
updated: 2025-10-03
---

<style>
Expand Down Expand Up @@ -137,17 +137,14 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
<table>
<tr>
<th>AWS</th>
<th>OVHcloud current mapping</th>
<th>OVHcloud mapping from 2025-06-04</th>
<th>OVHcloud</th>
</tr>
<tr>
<td>EXPRESS_ONEZONE</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>
Expand All @@ -158,7 +155,7 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
</tr>
<tr>
<td>STANDARD_IA</td>
<td rowspan=5>Standard Infrequent Access<sup>3</sup></td>
<td rowspan=5>Standard Infrequent Access</td>
</tr>
<tr>
<td>ONEZONE_IA</td>
Expand All @@ -175,7 +172,6 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
</table>

_<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-04._

The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the following:

Expand All @@ -194,19 +190,18 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the
</tr>
<tr>
<td>STANDARD_IA</td>
<td>Standard Infrequent Access<sup>3</sup></td>
<td>Standard Infrequent Access</td>
</tr>
</table>

_<sup>3</sup>: The Standard Infrequent Access tier will be available starting from 2025-06-04._

> [!warning]
> Unlike AWS, Express One Zone is treated as a regular storage class by OVHcloud and all our supported S3 compatible features and API operations are available.

### Endpoint retrocompatibility

> [!warning]
> - 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.
> 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 @@ -215,23 +210,20 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
<table>
<tr>
<th>AWS</th>
<th>OVHcloud current mapping</th>
<th>OVHcloud mapping from 2025-06-04</th>
<th>OVHcloud</th>
</tr>
<tr>
<td>EXPRESS_ONEZONE</td>
<td rowspan=3>High Performance</td>
<td rowspan=3>High Performance</td>
</tr>
<tr>
<td>STANDARD</td>
</tr>
<tr>
<td>default<sup>4</sup></td>
<td>default<sup>3</sup></td>
</tr>
<tr>
<td>STANDARD_IA</td>
<td rowspan=6>Standard</td>
<td rowspan=3>Standard</td>
</tr>
<tr>
Expand All @@ -242,7 +234,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>
<td rowspan=3>Standard Infrequent Access</td>
</tr>
<tr>
<td>GLACIER</td>
Expand All @@ -252,8 +244,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
</tr>
</table>

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

Expand All @@ -272,11 +263,10 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t
</tr>
<tr>
<td>GLACIER_IR</td>
<td>Standard Infrequent Access<sup>3</sup></td>
<td>Standard Infrequent Access</td>
</tr>
</table>

_<sup>3</sup>: The Standard Infrequent Access tier will be available starting from 2025-06-04._

## Object Storage Swift

Expand Down
30 changes: 10 additions & 20 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: 2025-06-04
updated: 2025-10-03

---

Expand Down Expand Up @@ -138,17 +138,14 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
<table>
<tr>
<th>AWS</th>
<th>OVHcloud current mapping</th>
<th>OVHcloud mapping from 2025-06-04</th>
<th>OVHcloud</th>
</tr>
<tr>
<td>EXPRESS_ONEZONE</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>
Expand All @@ -159,7 +156,7 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
</tr>
<tr>
<td>STANDARD_IA</td>
<td rowspan=5>Standard Infrequent Access<sup>3</sup></td>
<td rowspan=5>Standard Infrequent Access</td>
</tr>
<tr>
<td>ONEZONE_IA</td>
Expand All @@ -176,7 +173,6 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
</table>

_<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-04._

The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the following:

Expand All @@ -195,19 +191,18 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the
</tr>
<tr>
<td>STANDARD_IA</td>
<td>Standard Infrequent Access<sup>3</sup></td>
<td>Standard Infrequent Access</td>
</tr>
</table>

_<sup>3</sup>: The Standard Infrequent Access tier will be available starting from 2025-06-04._

> [!warning]
> Unlike AWS, Express One Zone is treated as a regular storage class by OVHcloud and all our supported S3 compatible features and API operations are available.

### Endpoint retrocompatibility

> [!warning]
> - 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.
> 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 @@ -216,23 +211,20 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
<table>
<tr>
<th>AWS</th>
<th>OVHcloud current mapping</th>
<th>OVHcloud mapping from 2025-06-04</th>
<th>OVHcloud</th>
</tr>
<tr>
<td>EXPRESS_ONEZONE</td>
<td rowspan=3>High Performance</td>
<td rowspan=3>High Performance</td>
</tr>
<tr>
<td>STANDARD</td>
</tr>
<tr>
<td>default<sup>4</sup></td>
<td>default<sup>3</sup></td>
</tr>
<tr>
<td>STANDARD_IA</td>
<td rowspan=6>Standard</td>
<td rowspan=3>Standard</td>
</tr>
<tr>
Expand All @@ -243,7 +235,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>
<td rowspan=3>Standard Infrequent Access</td>
</tr>
<tr>
<td>GLACIER</td>
Expand All @@ -253,8 +245,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
</tr>
</table>

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

Expand All @@ -273,11 +264,10 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t
</tr>
<tr>
<td>GLACIER_IR</td>
<td>Standard Infrequent Access<sup>3</sup></td>
<td>Standard Infrequent Access</td>
</tr>
</table>

_<sup>3</sup>: The Standard Infrequent Access tier will be available starting from 2025-06-04._

## Object Storage Swift

Expand Down
30 changes: 10 additions & 20 deletions pages/storage_and_backup/object_storage/s3_location/guide.en-au.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: 2025-06-04
updated: 2025-10-03
---

<style>
Expand Down Expand Up @@ -137,17 +137,14 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
<table>
<tr>
<th>AWS</th>
<th>OVHcloud current mapping</th>
<th>OVHcloud mapping from 2025-06-04</th>
<th>OVHcloud</th>
</tr>
<tr>
<td>EXPRESS_ONEZONE</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>
Expand All @@ -158,7 +155,7 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
</tr>
<tr>
<td>STANDARD_IA</td>
<td rowspan=5>Standard Infrequent Access<sup>3</sup></td>
<td rowspan=5>Standard Infrequent Access</td>
</tr>
<tr>
<td>ONEZONE_IA</td>
Expand All @@ -175,7 +172,6 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
</table>

_<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-04._

The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the following:

Expand All @@ -194,19 +190,18 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the
</tr>
<tr>
<td>STANDARD_IA</td>
<td>Standard Infrequent Access<sup>3</sup></td>
<td>Standard Infrequent Access</td>
</tr>
</table>

_<sup>3</sup>: The Standard Infrequent Access tier will be available starting from 2025-06-04._

> [!warning]
> Unlike AWS, Express One Zone is treated as a regular storage class by OVHcloud and all our supported S3 compatible features and API operations are available.

### Endpoint retrocompatibility

> [!warning]
> - 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.
> 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 @@ -215,23 +210,20 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
<table>
<tr>
<th>AWS</th>
<th>OVHcloud current mapping</th>
<th>OVHcloud mapping from 2025-06-04</th>
<th>OVHcloud</th>
</tr>
<tr>
<td>EXPRESS_ONEZONE</td>
<td rowspan=3>High Performance</td>
<td rowspan=3>High Performance</td>
</tr>
<tr>
<td>STANDARD</td>
</tr>
<tr>
<td>default<sup>4</sup></td>
<td>default<sup>3</sup></td>
</tr>
<tr>
<td>STANDARD_IA</td>
<td rowspan=6>Standard</td>
<td rowspan=3>Standard</td>
</tr>
<tr>
Expand All @@ -242,7 +234,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>
<td rowspan=3>Standard Infrequent Access</td>
</tr>
<tr>
<td>GLACIER</td>
Expand All @@ -252,8 +244,7 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
</tr>
</table>

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

Expand All @@ -272,11 +263,10 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t
</tr>
<tr>
<td>GLACIER_IR</td>
<td>Standard Infrequent Access<sup>3</sup></td>
<td>Standard Infrequent Access</td>
</tr>
</table>

_<sup>3</sup>: The Standard Infrequent Access tier will be available starting from 2025-06-04._

## Object Storage Swift

Expand Down
Loading