Skip to content

OVH

Authentication

OVH Public Cloud uses application-based authentication with three credentials plus a project ID. To get started:

  1. Create application credentials at the OVH API console (or api.us.ovhcloud.com for US)
  2. Authorize a consumer key with the required API permissions
  3. Find your Public Cloud project ID in the OVH Control Panel under your project's details
FieldRequiredDescription
endpointYesAPI endpoint: ovh-eu, ovh-us, or ovh-ca
application_keyYesApplication key from OVH API console
application_secretYesApplication secret from OVH API console
consumer_keyYesConsumer key (authorized token)
project_idYesPublic Cloud project ID

Configuration

yaml
providers:
  ovh:
    endpoint: ovh-eu
    application_key: "${OVH_APP_KEY}"
    application_secret: "${OVH_APP_SECRET}"
    consumer_key: "${OVH_CONSUMER_KEY}"
    project_id: "${OVH_PROJECT_ID}"
    region: GRA9
    image: Ubuntu 22.04
    size: b2-7

defaults:
  provider: ovh

Endpoints

Choose the endpoint closest to your account region:

EndpointAPI URL
ovh-euhttps://eu.api.ovh.com/1.0
ovh-ushttps://api.us.ovhcloud.com/1.0
ovh-cahttps://ca.api.ovh.com/1.0

Regions

OVH regions use datacenter codes:

SlugLocation
GRA7, GRA9, GRA11Gravelines, France
SBG5Strasbourg, France
BHS5Beauharnois, Canada
DE1Frankfurt, Germany
UK1London, UK
WAW1Warsaw, Poland
SYD1Sydney, Australia
SGP1Singapore

Run managed providers regions ovh to list all available regions for your project.

Sizes

OVH uses flavor names that indicate the instance category:

SlugSpecs
d2-21 vCPU, 2 GB RAM, 25 GB disk
d2-42 vCPU, 4 GB RAM, 50 GB disk
d2-84 vCPU, 8 GB RAM, 50 GB disk
b2-72 vCPU, 7 GB RAM, 50 GB disk
b2-154 vCPU, 15 GB RAM, 100 GB disk
b2-308 vCPU, 30 GB RAM, 200 GB disk

Prefix meanings: d2 = general purpose, b2 = balanced, c2 = CPU-optimized, r2 = RAM-optimized.

Run managed providers sizes ovh --region GRA7 to list all available flavors in a region.

Images

OVH images are referenced by name. The provider resolves names to the underlying OpenStack image UUIDs automatically:

NameOS
Ubuntu 22.04Ubuntu 22.04 LTS
Ubuntu 24.04Ubuntu 24.04 LTS
Debian 12Debian 12

Auto storage

OVH does not support auto-provisioned storage. OVH offers S3-compatible Object Storage, but credentials must be created manually through the OpenStack Horizon dashboard or API. Configure storage in managed.yaml:

yaml
storage:
  endpoint: "s3.gra.io.cloud.ovh.net"
  region: "gra"
  bucket: "my-backups"
  access_key: "${OVH_S3_ACCESS_KEY}"
  secret_key: "${OVH_S3_SECRET_KEY}"

Bare-metal servers

OVH also rents bare-metal (dedicated) servers. You order one yourself in the OVH manager, then point managed at it with kind: dedicated, managed adopts the box you already have rather than creating one. See Use your own server for the config shape.

One thing to do before you run managed apply on a bare-metal box: set up its disks and RAID in the OVH manager. managed apply never touches disks, so this is a one-time manual step, and if you're running a database, getting it right is what keeps your data safe when a disk fails. The full walkthrough is in Storage & RAID on OVH bare metal.

Networking

OVH Public Cloud instances receive both public and private IPs when attached to a private network (vRack). Managed uses private IPs for inter-server communication when available.