Connect Google Cloud
Give Rowsafe a service account key for a project of its own so it can create database servers (Compute Engine VMs) there.
To create servers for you in Google Cloud, Rowsafe needs a service account key for a project of its own. It takes about five minutes.
Create the service account and its key
Create a project
In the Google Cloud console, create a project just for these databases (project picker, New project) with billing on. The roles reach the whole project, so a project of its own keeps everything else out of reach.
Turn on the APIs
Open APIs & Services, Enable APIs and services, and turn on Compute Engine API and Cloud Resource Manager API.
Create the service account
Open IAM & Admin, Service accounts, Create service account. Name it rowsafe. Give it Compute Instance Admin (v1), Compute Network Admin and Compute Security Admin (or a custom role), then click Done.
Create a key
Open the service account, Keys, Add key, Create new key, JSON, Create. A file downloads.
If an organization policy blocks key creation, your Google Cloud admin has to allow it for this project.
Paste it into Rowsafe
In the dashboard, open Settings → Cloud accounts (or Create a server for me) and click Connect a cloud account. Choose Google Cloud, paste the whole file into Service account key (JSON), name the account and click Connect. Leave Project ID empty to use the service account's project.
Then delete the downloaded file.
Rowsafe checks the key first, without creating anything, and names any missing permission.
What access this gives Rowsafe
The three roles, on the project:
| Role | ID |
|---|---|
| Compute Instance Admin (v1) | roles/compute.instanceAdmin.v1 |
| Compute Network Admin | roles/compute.networkAdmin |
| Compute Security Admin | roles/compute.securityAdmin |
They cover every VM, disk, firewall rule and address in the project, and nothing outside Compute Engine or in other projects. For less, create a custom role (IAM & Admin, Roles, Create role) with exactly these permissions:
compute.projects.get
compute.regions.get
compute.regions.list
compute.instances.create
compute.instances.delete
compute.instances.get
compute.instances.list
compute.instances.setMetadata
compute.instances.setLabels
compute.instances.setTags
compute.instances.setMachineType
compute.instances.start
compute.instances.stop
compute.disks.create
compute.disks.setLabels
compute.images.useReadOnly
compute.networks.get
compute.networks.updatePolicy
compute.subnetworks.use
compute.subnetworks.useExternalIp
compute.firewalls.create
compute.firewalls.delete
compute.firewalls.get
compute.firewalls.list
compute.firewalls.update
compute.addresses.create
compute.addresses.delete
compute.addresses.get
compute.addresses.use
compute.addresses.setLabels
compute.zoneOperations.get
compute.regionOperations.get
compute.globalOperations.getFor each server, Rowsafe creates a Debian 12 VM with its disk, a static public address, and firewall rules on the default network letting in only your addresses, all labelled rowsafe=1. Your SSH keys go on the VM only if you give them (never Rowsafe's own); project-wide SSH keys are blocked on it. Only when someone clicks and confirms. See what Rowsafe does with your cloud account.
Revoke it
- In Google Cloud: IAM & Admin, Service accounts,
rowsafe, Keys: delete the key. Or delete the service account. - In Rowsafe: Settings → Cloud accounts, Remove (once its servers are deleted). Nothing in your project changes.
Your servers keep running and stay protected. Resize, firewall changes and deletes then happen in the Google Cloud console.
Good to know
- Prices are "about": estimates from Google Cloud list prices in one region. Your Google Cloud bill is what counts.
- The project needs its
defaultnetwork. New projects have one; if it's gone, Rowsafe says so.