OVHcloud
OVHcloud names its regions after datacenters — gra for Gravelines, sbg for Strasbourg, bhs for Beauharnois — rather than after compass directions. Credentials are not account-level: you create a user inside a Public Cloud project and grant it an object storage role.
Connection settings
- Endpoint
- https://s3.{region}.cloud.ovh.net
- Default region
- gra
- Addressing
- Virtual-hosted
- Temporary credentials
- Not applicable
A filled-in example
Every value below is fabricated — they are shaped like real OVHcloud credentials so you can recognise yours, and they authenticate nothing.
- Endpoint
- https://s3.gra.cloud.ovh.net
- Region
- gra
- Access key
- example0ovhaccesskey00000000000a
- Secret key
- example0ovhsecretkey00000000000b
- Addressing
- Virtual-hosted
gra is Gravelines, in northern France. The full list in the app is gra, sbg, bhs, de, uk and waw.
Where each value comes from
Endpoint
Format: https://s3.{region}.cloud.ovh.net — Regions are OVH datacenter codes (gra, sbg, bhs, etc.).
Credentials
In OVHcloud Control Panel → Public Cloud → Project → Users & Roles, create a user with Object Storage permissions.
Notes
OVH regions correspond to datacenter locations. The S3 API is available on their Public Cloud offering.
What usually goes wrong
Two object storage products share a name
OVHcloud offers a Swift-based storage and an S3-compatible one. Only the latter answers on s3.{region}.cloud.ovh.net. If your container was created through the Swift interface it will not appear over S3.
The user needs an explicit role
Creating a user under Users & Roles is not enough — it must be given an object storage role, and the S3 credentials are generated separately once that role is attached.
Region codes are not interchangeable with AWS
There is no eu-west-1 here. Scripts carried over from AWS will fail on the region value before they ever reach authentication.
Regions available in the app
grasbgbhsdeukwaw