Have a unique endpoint for Standard S3 & Highperf S3

[lason-ovh]

As an OVHcloud customer using both HighPerf S3 & Standard S3 I want a unique endpoint for both storage classes so that it simplifies a lot the configuration management of my applications by NOT having to manage 2 endpoints (switch between standard & highperf, maintain & update rules to chose between the 2, ...etc)

Furthermore, having one unique endpoint for all the storage classes is a prerequisite to lifecycle management as an object would transition automatically from a storage class to another.

What will be supported:

• a unique endpoint for all the storage classes (Standard & Highperf) to create, get, delete objects in a given region

Limitations:

• the endpoint will still be region specific

Impacts:

• perf endpoint: will still be supported for backwards compatibility
• io endpoint: will support both Highperf & Standard storage classes

[lason-ovh]

Hi all,

As part of our ongoing commitment to improving our offerings and providing a seamless, enriched experience for all our customers, we'd like to inform you of an update to the way you consume our services, while minimizing the impact for you.

The aim is to enable you to address all our storage classes on a single .io endpoint, while ensuring backward compatibility with the current operation of your tools via the .perf endpoint.

This change is motivated by : • our desire to better position our High Performance offering in the market and to better highlight the specific use cases for this class of storage. • greater consistency with the ultimate objective of optimizing storage costs when used together in our next lifecycle feature to move from a hot to a less hot storage class.

This change will take place in 2 stages: • June 10, 2024: Modification of storage classes associated with endpoints. • June 17, 2024: Removal of the constraint of a single storage class per bucket. From this day on, the storage class can be specified per object, opening new possibilities for the consumption of Object Storage offers.

Unless a specific storage class configuration is in place on your software, no change/impact is to be expected. If not, please refer to our dedicated page for storage class correspondence by offer: https://help.ovhcloud.com/csm/en-public-cloud-storage-s3-location?id=kb_article_view&sysparm_article=KB0047384

[lason-ovh]

Hi all,

This is a simple reminder of the upcoming update that we previously shared with you a few weeks ago regarding our S3 Object Storage (Standard and/or High Performance).

As a quick recap, the aim of this update is to enable you to benefit from a single entry point, the .io endpoint, for all our storage classes in order to create/read/delete objects and buckets, while ensuring backward compatibility with the current way your tools work via the .perf endpoint.

All of this is designed to enhance your experience with the service. We believe that these changes will be of great value to you.

Here's a brief overview of what you can expect:

June 10, 2024: Modification of storage classes associated with endpoints. June 17, 2024: Removal of the constraint of a single storage class per bucket. From this day on, the storage class can be specified per object, opening up new possibilities for consuming Object Storage offerings. As shared, for further details please refer to our dedicated page : https://help.ovhcloud.com/csm/en-ca-public-cloud-storage-s3-location?id=kb_article_view&sysparm_article=KB0047381

In the meantime, if you have any questions or concerns about the update, please don't hesitate to reach out to us on Discord or through our technical support : https://discord.com/channels/850031577277792286/893523544846270504

Thank you

[lason-ovh]

Hi all, As a reminder, we have proceeded today with the update that was communicated several weeks ago on our Object Storage S3 (Standard and High Performance) endpoints. This update is to enable you to benefit from a single entry point, the .io endpoint, for all our storage classes in order to create/read/delete objects and buckets, while ensuring backward compatibility with the current way your tools work via the .perf endpoint. We have removed the constraint of a single storage class per bucket. From this day on, the storage class can be specified per object, opening up new possibilities for consuming Object Storage offerings. You can find the details of this update in the dedicated page : https://help.ovhcloud.com/csm/en-caen-ca-public-cloud-storage-s3-location?id=kb_article_view&sysparm_article=KB0047381 We remain available to answer any questions you may have in our Discord channel: https://discord.com/channels/850031577277792286/893523544846270504