Skip to content

SSH keys on Quake AI

Explanation · Updated Jun 2026

Coming from another cloud?

▸AWS·EC2 Key Pairs

EC2 Key Pairshigh

  • Public key auto-injected to authorized_keys at boot.
  • Up to 5000 per region; AWS stores public key.
  • Supports import of external keys (RSA/ED25519).
  • No post-launch addition without userdata/SSM.
AWS docs ↗
▸Azure·SSH public keys

SSH public keyshigh

  • Managed as ARM resources (Microsoft.Compute/sshPublicKeys), reusable across VMs, vs OpenStack's keypairs injected only at boot.
  • API /providers/Microsoft.Compute/sshPublicKeys, supports ED25519/RSA, no private key storage.
  • Keys provided during VM create or via portal/CLI, not listed/injected separately post-boot like OpenStack.
  • No deletion/re-import of injected keys; new VM for changes.
Azure docs ↗
▸DigitalOcean·SSH keys (Account/Team SSH keys)

SSH keys (Account/Team SSH keys)high

  • SSH keys are managed at the account/team level via /v2/account/keys and then referenced by ID/fingerprint when creating Droplets, whereas OpenStack Nova keypairs are typically created per project/tenant and managed via the Nova API.
  • DigitalOcean explicitly notes that including a key during Droplet creation embeds it into the root user’s authorized_keys, whereas OpenStack’s keypair injection mechanism is generally cloud-init/metadata-service driven and may vary by image/cloud config.
  • DigitalOcean tokens/scopes model for API authorization (bearer tokens with scopes like ssh_key:read) differs from OpenStack Keystone’s token + role-based policy model.
  • DigitalOcean documentation emphasizes that post-creation SSH key changes are performed inside the guest OS (not via control panel), whereas OpenStack users may rely more heavily on metadata/cloud-init or config management patterns post-boot.
DigitalOcean docs ↗
▸Google Cloud·SSH keys

SSH keyshigh

  • Managed in project/instance metadata or OS Login (IAM); no central 'keypairs' resource like Nova.
  • Auto-generates ephemeral keys for CLI/console; manual upload only in OpenStack.
  • Public key includes username suffix; injected differently.
Google Cloud docs ↗
▸Hetzner·SSH Keys

SSH Keyshigh

  • API /v1/ssh_keys; POST public_key, name; inject array of ssh_keys on server create.
  • No private key management; user provides public keys only.
  • Fingerprint-based listing/filtering; labels support.
  • Injected via cloud-init on boot.
Hetzner docs ↗

SSH keys on Quake AI

SSH keys in migration guides and provider consoles map to key pairs on Quake AI: a stored public key Nova injects at instance boot through cloud-init, paired with the private key you keep on your workstation.

The Console and API label the resource key pair. Tutorials that say "upload your SSH key" mean create or import a key pair, then select it at instance launch.

Provider mapping#

ProviderTheir termOn Quake AI
AWSEC2 key pairKey pair
AzureSSH public keyKey pair
Google CloudSSH key / OS LoginKey pair (OS Login patterns differ)
Hetzner / DigitalOceanSSH keyKey pair

Generate keys with ssh-keygen (Ed25519 recommended). See add an SSH key for Console and CLI import steps.

Related content

Was this page helpful?