Connect OVHcloud
Give Rowsafe OVHcloud API keys limited to one Public Cloud project so it can create database servers there.
To create servers for you in OVHcloud, Rowsafe needs API keys limited to one Public Cloud project. It takes about five minutes.
Create the keys
Open a Public Cloud project just for Rowsafe
Sign in to the OVHcloud Control Panel, open Public Cloud and create a project for your databases (add a payment method if asked). The keys reach only this project.
Copy the project ID: the 32 letters and digits under the project's name.
Create the API keys
Open the createToken page for your account's region and sign in:
- Europe and the rest of the world:
https://eu.api.ovh.com/createToken - Canada:
https://ca.api.ovh.com/createToken - United States:
https://api.us.ovhcloud.com/createToken
Name the application Rowsafe, set Validity to Unlimited, and add only these three rights, with your project ID:
GET /cloud/project/PROJECT_ID/*
POST /cloud/project/PROJECT_ID/*
DELETE /cloud/project/PROJECT_ID/*Click Create keys and copy the application key, application secret and consumer key.
Paste them into Rowsafe
In the dashboard, open Settings → Cloud accounts (or Create a server for me) and click Connect a cloud account. Choose OVHcloud Public Cloud, paste the project ID and the three keys, name the account and click Connect. Leave OVHcloud region empty: Rowsafe finds it.
Rowsafe checks the keys first: that they work, can read the project, and that the project is active.
What access this gives Rowsafe
The three rights above, on this project only: no orders, billing or other services.
Rowsafe only touches what it creates:
- instances (Debian 13, else Debian 12 or Ubuntu 24.04), only when someone clicks and confirms;
- security groups named
rowsafe-plus the instance ID, letting in only your addresses, where the quota allows (the firewall); - SSH keys, only the ones you give it (never its own), kept for reuse after a server is deleted;
- one project user, "Rowsafe firewall", with network roles only, to set the security groups. Nobody keeps its password: Rowsafe sets a new one each time and trades it for a short-lived token.
OVHcloud has no labels, so Rowsafe finds its servers by ID and name. See what Rowsafe does with your cloud account.
The firewall
New Public Cloud projects allow no security groups until OVHcloud support raises the quota. Then Rowsafe puts the firewall on the server itself:
- The Rowsafe agent sets the rules (nftables, IPv4 and IPv6, kept across reboots) once installed, and again when you change Who can connect. The server's page says when they're applied.
- In the first minutes after boot, OVHcloud's default rules let everything in. Only SSH is exposed then, and it accepts only your keys. The database isn't reachable: its port is closed before it listens on the network.
- The server's permission to change its own firewall is turned on, since that's how Who can connect works there.
A server keeps the firewall it was created with. Servers created after the quota is raised get a security group.
Quotas
Each project has quotas per region (instances, CPUs, memory, security groups), and new projects start small. When a server doesn't fit, Rowsafe says so: raise the quota (Public Cloud, Quota and regions), delete a server, or pick another region.
Revoke it
- In OVHcloud: delete the
Rowsafeapplication's keys in the Control Panel, or withDELETE /me/api/credential/{id}. They stop working at once. - In Rowsafe: Settings → Cloud accounts, Remove (once its servers are deleted). Nothing in OVHcloud changes.
Your servers keep running and stay protected. Resize, cloud firewall changes and deletes then happen in the Control Panel. Where the firewall is on the server, Who can connect keeps working.
Good to know
- Prices are "about": OVHcloud's hourly catalog price times 730, in your account's currency (EUR, CAD or USD). A 31-day month costs a little more. Your OVHcloud bill is what counts.
- Local zones (regions named
-LZ-) aren't offered. - Log in over SSH as
debian(orubuntuwhere the region only has Ubuntu) with your key.