VPS Snaps

Connect Google Cloud without a sign-in

Connect a Google Cloud project in one click, through Workload Identity Federation: no key, no Google sign-in to expire, and access you revoke by deleting one pool.

A Google Cloud connection made by signing in with Google belongs to the person who signed in. A Google Workspace can end it every few hours, and it stops when they leave. A keyless connection has neither problem: VPS Snaps acts as a service account in your project through Workload Identity Federation, so no key is created and nobody's sign-in is involved.

Connect in one click

  • In VPS Snaps, go to Providers → Add provider → Google Cloud, enter the project ID, and choose Connect Google Cloud.
  • Sign in with Google as someone who can manage permissions in the project, such as an owner. Google asks you to allow Google Cloud access for this step.
  • VPS Snaps sets the project up, waits for Google to apply the new permissions, which can take a minute or two, and lists your instances to prove it works.
  • Your sign-in is then dropped. It is never saved, and nothing about the connection depends on it.

To switch a connection you made by signing in, open it under Providers and choose Switch in one click. Its backup jobs keep running, and the old sign-in is no longer used.

Or run the setup yourself

If you would rather not sign in, or someone else manages the project, the same setup is a set of commands. Choose Or run the setup commands yourself on the connect page, run them in Cloud Shell as someone who can manage IAM in the project, and paste back the project number the last one prints. They are written for your workspace and no other.

What is created in your project

  • A service account named vpssnaps. It gets Compute Instance Admin for machine images and the instances recovery servers and test restores build, Compute Security Admin for their firewall rules, and Compute Network Viewer to read addresses for failover.
  • A workload identity pool and provider, both named vpssnaps, that trust https://vpssnaps.com/oidc/gcp only for statements naming your VPS Snaps workspace.
  • A binding that lets that one workspace act as the service account.

No key is created at any point. VPS Snaps signs a five-minute statement with its own key, Google exchanges it for a one-hour token, and that token works only as the vpssnaps service account in your project.

Revoking it

Delete the vpssnaps workload identity pool, and VPS Snaps can no longer act in the project. You can delete the service account as well. A deleted pool keeps its name for 30 days, so to set it up again within that time, undelete the pool rather than creating a new one.

gcloud iam workload-identity-pools delete vpssnaps --location=global --project=PROJECT_ID

If verifying fails

  • Could not find the workload identity provider: check the project number, and that every command finished without an error.
  • Set up for a different VPS Snaps workspace: the commands were copied from another workspace. Run the ones shown in this one.
  • May not act as the service account: the last binding command, roles/iam.workloadIdentityUser, did not run.
  • Compute Engine refused to list instances: a role binding did not run, or the Compute Engine API was enabled moments ago. Wait a minute and verify again.

Still stuck?

Open the failed run under Backup History and copy the error text out of the log — pasting that into your first message is usually the difference between one reply and four.