All Collections › Clusters & Servers › How to configure OVHcloud credentials

How to configure OVHcloud credentials

Connect Hatchbox to an OVHcloud Public Cloud project with API keys

Updated

OVHcloud's Public Cloud runs hourly-billed servers in the US, Canada and Europe, for about half what DigitalOcean charges at each size. Hatchbox creates and manages them in one of your Public Cloud projects, with API keys that can only reach your Public Cloud projects.

OVHcloud US is a separate company from OVHcloud in Europe and Canada, with its own accounts, so use the steps and links for the one you signed up with.

Create a Public Cloud project

In the OVHcloud Control Panel, open Public Cloud and create a project if you don't have one. Copy its project ID, the long string of letters and numbers shown in the project's settings and its URL.

Create API keys for Hatchbox

Open the key page for your OVHcloud. These links fill in access to your Public Cloud projects only:

Sign in, name the keys Hatchbox, and set the validity to Unlimited, or the keys stop working when they expire. OVHcloud then shows an Application Key, an Application Secret and a Consumer Key. Copy all three; the secret and consumer key are only shown once.

Connect a cluster

Create a new cluster, choose OVHcloud, and enter which OVHcloud your account is with, the project ID and the three keys. Then pick a region and add your servers. Hatchbox only lists the regions that run servers, such as US-EAST-VA-1, and skips the storage-only regions a project also has. The sizes are OVHcloud's flavors, like d2-4 (Discovery, the cheapest) and b3-8 (General Purpose), billed by the hour.

Private network

A cluster's servers talk to each other over a private network on your project's vRack, rather than their public network, which is slower on the smaller flavors and goes over the internet. The vRack is free. If your project doesn't have one, Hatchbox orders it for you when it creates the cluster's first server. If that order doesn't go through, the server's log says so; open your project in the Control Panel, create the vRack under Network > Private Network, and create the server again.

Each cluster gets its own private network on the vRack, so clusters in the same project stay apart.

Removing access

To revoke Hatchbox's access, delete the keys in the Control Panel under Identity, Security & Operations > API keys. Hatchbox can't create, update or delete servers in the project after that.