Skip to content
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

Jump to bottom

Lso update s3 guides merge endpoints #6189

Merged
merged 28 commits into from
May 20, 2024
Merged

Lso update s3 guides merge endpoints #6189

Show file tree
Hide file tree
Changes from 22 commits
Commits
Show all changes
28 commits
Select commit Hold shift + click to select a range
73a5ac3
Update guide.en-gb.md
lason-ovh Mar 8, 2024
748c310
Update guide.en-gb.md
lason-ovh Mar 8, 2024
eba6d6e
Update guide.en-gb.md
lason-ovh Mar 8, 2024
5f68622
Update guide.en-gb.md
lason-ovh Mar 8, 2024
d6e69e8
Update guide.en-gb.md
lason-ovh Mar 8, 2024
dfe8040
Update guide.en-gb.md
lason-ovh Mar 8, 2024
10bee35
Update guide.en-gb.md
lason-ovh Mar 26, 2024
de58367
EN proof Add duplos
Apr 24, 2024
e336529
Add duplos
Apr 24, 2024
d6fea7d
Add duplos
Apr 24, 2024
d2bb7bc
Add duplos
Apr 24, 2024
9453dc3
Add duplos
Apr 24, 2024
3d79c91
Add duplos
Apr 24, 2024
a435e6a
Minor fixes and dates update
Y0Coss May 7, 2024
19c51ce
Merge branch 'develop' into LSO_update_s3_guides_merge_endpoints
OVH-Team-Guides May 7, 2024
16d4920
Update guide.en-gb.md
lason-ovh May 14, 2024
5bacf39
Create images
lason-ovh May 14, 2024
695560c
Proofreading - duplication - FR translation - deleting images file
Y0Coss May 15, 2024
b7854d7
initialize /images dir with temp file
lason-ovh May 15, 2024
5d07b6a
added endpoint mapping schemas
lason-ovh May 15, 2024
d5c8e74
Delete temp file
lason-ovh May 15, 2024
b00af59
added mapping schemas to summarize mapping for each endpoint
lason-ovh May 15, 2024
63ec9dd
Proofreading + FR version + duplication
Y0Coss May 15, 2024
41c360b
FR typo fix
Y0Coss May 15, 2024
df8ab97
added new supported regions
lason-ovh May 15, 2024
b01b7aa
added mention about listing of buckets in perf endpoint
lason-ovh May 16, 2024
a6427fc
added warning
lason-ovh May 16, 2024
d7e13e6
Minor fix - FR trans - Duplication - Dates update
Y0Coss May 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
160 changes: 152 additions & 8 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-03-01
updated: 2024-05-15
---

<style>
Expand All @@ -11,18 +11,162 @@ td:nth-of-type(2) {

We have designed the S3 storage classes to be **compatible with the 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.

## List of endpoints by region and storage class
## Object Storage S3

| Storage class | endpoint URL | Region available<br><b><i>To be entered in lower case</i></b> |
OVHcloud Object Storage S3 can now be accessed through a unique endpoint: `https://s3.<region>.io.cloud.ovh.net`. This unique endpoint can address both Standard and High Performance storage classes. All S3 API operations are supported with this unique endpoint.

### List of available regions

| Region name | Region<br><b><i>To be entered in lower case</i></b> | Protocol | Signature version |
| ------ | ------ | ------ | ------ |
| Gravelines | gra | HTTPS | 4 |
| Frankfurt | de | HTTPS | 4 |
| Beauharnois | bhs | HTTPS | 4 |
| Roubaix | rbx | HTTPS | 4 |
| Warsaw | waw | HTTPS | 4 |
| London | uk | HTTPS | 4 |

The bucket endpoint is a URL, for example `https://my-bucket.s3.gra.io.cloud.ovh.net` that represents a virtual host style endpoint.

### Mapping from AWS S3 Storage tiers to OVHcloud Storage tiers

The **io** endpoint is be the preferred endpoint to access the OVHcloud Object Storage service.

The mapping for **WRITE(PUT)** operations on the **io** endpoint is the following:

<table>
<tr>
<th>AWS</th>
<th>OVHcloud current mapping</th>
<th>OVHcloud target mapping (from 2024-06-17)</th>
</tr>
<tr>
<td>Express One Zone</td>
<td rowspan=9>Standard</td>
<td>High Performance</td>
</tr>
<tr>
<td>Standard</td>
<td rowspan=8>Standard</td>
</tr>
<tr>
<td>default*</td>
</tr>
<tr>
<td>Standard IA</td>
</tr>
<tr>
<td>Intelligent Tiering</td>
</tr>
<tr>
<td>One Zone IA</td>
</tr>
<tr>
<td>Glacier Instant Retrieval</td>
</tr>
<tr>
<td>Glacier Flexible</td>
</tr>
<tr>
<td>Glacier Deep Archive</td>
</tr>
</table>

*_the default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class or if you specify a storage class other than those provided by AWS, your object will be stored in our Standard tier._

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

<table>
<tr>
<th>AWS</th>
<th>OVHcloud target mapping (from 2024-06-17)</th>
</tr>
<tr>
<td>Express One Zone</td>
<td>High Performance</td>
</tr>
<tr>
<td>Standard</td>
<td>Standard</td>
</tr>
</table>

> [!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 **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.

The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the following:

<table>
<tr>
<th>AWS</th>
<th>OVHcloud current mapping</th>
<th>OVHcloud target mapping (from 2024-06-10)</th>
</tr>
<tr>
<td>Express One Zone</td>
<td rowspan=9>High Performance</td>
<td rowspan=3>High Performance</td>
</tr>
<tr>
<td>Standard</td>
</tr>
<tr>
<td>default*</td>
</tr>
<tr>
<td>Standard IA</td>
<td rowspan=6>Standard</td>
</tr>
<tr>
<td>Intelligent Tiering</td>
</tr>
<tr>
<td>One Zone IA</td>
</tr>
<tr>
<td>Glacier Instant Retrieval</td>
</tr>
<tr>
<td>Glacier Flexible</td>
</tr>
<tr>
<td>Glacier Deep Archive</td>
</tr>
</table>

*_the default storage class on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class or if you specify a storage class other than those provided by AWS, 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 target mapping (from 2024-06-10)</th>
</tr>
<tr>
<td>Standard</td>
<td>High Performance</td>
</tr>
<tr>
<td>Standard IA</td>
<td>Standard</td>
</tr>
</table>

## Object Storage Swift

| Storage solution | endpoint URL | Region available<br><b><i>To be entered in lower case</i></b> |
| ------ | ------ | ------ |
| Object Storage S3 - Standard | `https://s3.<region>.io.cloud.ovh.net` | Gravelines: gra<br>Strasbourg: sbg<br> Frankfurt: de <br>Beauharnois: bhs <br>Roubaix: rbx <br>Warsaw: waw <br>London: uk |
| Object Storage S3 - High Performance |`https://s3.<region>.perf.cloud.ovh.net` | Gravelines: gra<br>Strasbourg: sbg<br>Beauharnois: bhs<br>London: uk<br>Frankfurt: de<br>Warsaw: waw<br>Roubaix: rbx |
| Object Storage SWIFT - Standard - Legacy |`https://s3.<region>.cloud.ovh.net` | Strasbourg: sbg<br>London: uk<br>Frankfurt: de<br>Warsaw: waw<br>Beauharnois: bhs<br>Gravelines: gra |

The bucket endpoint is a URL, for example `https://my-bucket.s3.gra.perf.cloud.ovh.net` that represents a virtual host style endpoint.

## Go further

If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/de/professional-services/) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.

Join our community of users on <https://community.ovh.com/en/>.
160 changes: 152 additions & 8 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-03-01
updated: 2024-05-15
---

<style>
Expand All @@ -11,18 +11,162 @@ td:nth-of-type(2) {

We have designed the S3 storage classes to be **compatible with the 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.

## List of endpoints by region and storage class
## Object Storage S3

| Storage class | endpoint URL | Region available<br><b><i>To be entered in lower case</i></b> |
OVHcloud Object Storage S3 can now be accessed through a unique endpoint: `https://s3.<region>.io.cloud.ovh.net`. This unique endpoint can address both Standard and High Performance storage classes. All S3 API operations are supported with this unique endpoint.

### List of available regions

| Region name | Region<br><b><i>To be entered in lower case</i></b> | Protocol | Signature version |
| ------ | ------ | ------ | ------ |
| Gravelines | gra | HTTPS | 4 |
| Frankfurt | de | HTTPS | 4 |
| Beauharnois | bhs | HTTPS | 4 |
| Roubaix | rbx | HTTPS | 4 |
| Warsaw | waw | HTTPS | 4 |
| London | uk | HTTPS | 4 |

The bucket endpoint is a URL, for example `https://my-bucket.s3.gra.io.cloud.ovh.net` that represents a virtual host style endpoint.

### Mapping from AWS S3 Storage tiers to OVHcloud Storage tiers

The **io** endpoint is be the preferred endpoint to access the OVHcloud Object Storage service.

The mapping for **WRITE(PUT)** operations on the **io** endpoint is the following:

<table>
<tr>
<th>AWS</th>
<th>OVHcloud current mapping</th>
<th>OVHcloud target mapping (from 2024-06-17)</th>
</tr>
<tr>
<td>Express One Zone</td>
<td rowspan=9>Standard</td>
<td>High Performance</td>
</tr>
<tr>
<td>Standard</td>
<td rowspan=8>Standard</td>
</tr>
<tr>
<td>default*</td>
</tr>
<tr>
<td>Standard IA</td>
</tr>
<tr>
<td>Intelligent Tiering</td>
</tr>
<tr>
<td>One Zone IA</td>
</tr>
<tr>
<td>Glacier Instant Retrieval</td>
</tr>
<tr>
<td>Glacier Flexible</td>
</tr>
<tr>
<td>Glacier Deep Archive</td>
</tr>
</table>

*_the default storage class on the **io** endpoint will be Standard, i.e. if you don't specify a storage class or if you specify a storage class other than those provided by AWS, your object will be stored in our Standard tier._

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

<table>
<tr>
<th>AWS</th>
<th>OVHcloud target mapping (from 2024-06-17)</th>
</tr>
<tr>
<td>Express One Zone</td>
<td>High Performance</td>
</tr>
<tr>
<td>Standard</td>
<td>Standard</td>
</tr>
</table>

> [!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 **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.

The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the following:

<table>
<tr>
<th>AWS</th>
<th>OVHcloud current mapping</th>
<th>OVHcloud target mapping (from 2024-06-10)</th>
</tr>
<tr>
<td>Express One Zone</td>
<td rowspan=9>High Performance</td>
<td rowspan=3>High Performance</td>
</tr>
<tr>
<td>Standard</td>
</tr>
<tr>
<td>default*</td>
</tr>
<tr>
<td>Standard IA</td>
<td rowspan=6>Standard</td>
</tr>
<tr>
<td>Intelligent Tiering</td>
</tr>
<tr>
<td>One Zone IA</td>
</tr>
<tr>
<td>Glacier Instant Retrieval</td>
</tr>
<tr>
<td>Glacier Flexible</td>
</tr>
<tr>
<td>Glacier Deep Archive</td>
</tr>
</table>

*_the default storage class on the **perf** endpoint will be High Performance, i.e. if you don't specify a storage class or if you specify a storage class other than those provided by AWS, 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 target mapping (from 2024-06-10)</th>
</tr>
<tr>
<td>Standard</td>
<td>High Performance</td>
</tr>
<tr>
<td>Standard IA</td>
<td>Standard</td>
</tr>
</table>

## Object Storage Swift

| Storage solution | endpoint URL | Region available<br><b><i>To be entered in lower case</i></b> |
| ------ | ------ | ------ |
| Object Storage S3 - Standard | `https://s3.<region>.io.cloud.ovh.net` | Gravelines: gra<br>Strasbourg: sbg<br> Frankfurt: de <br>Beauharnois: bhs <br>Roubaix: rbx <br>Warsaw: waw <br>London: uk |
| Object Storage S3 - High Performance |`https://s3.<region>.perf.cloud.ovh.net` | Gravelines: gra<br>Strasbourg: sbg<br>Beauharnois: bhs<br>London: uk<br>Frankfurt: de<br>Warsaw: waw<br>Roubaix: rbx |
| Object Storage SWIFT - Standard - Legacy |`https://s3.<region>.cloud.ovh.net` | Strasbourg: sbg<br>London: uk<br>Frankfurt: de<br>Warsaw: waw<br>Beauharnois: bhs<br>Gravelines: gra |

The bucket endpoint is a URL, for example `https://my-bucket.s3.gra.perf.cloud.ovh.net` that represents a virtual host style endpoint.

## Go further

If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/asia/professional-services/) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.

Join our community of users on <https://community.ovh.com/en/>.