SSH keys for Cloud Pool VMs

SSH keys let you log in to Linux VMs without embedding a password. Keys are stored on your organization, then selected when you create a VM.

Add a key

1. Open Developer → SSH Keys.
2. Add a public key (typically the contents of id_ed25519.pub or id_rsa.pub).
3. Give it a memorable name (for example laptop-alice).

Keys are shared with technical users on the organization — anyone creating a VM can select them.

Use keys when creating a VM

1. Start the create VM wizard (see Create a virtual machine in a Cloud Pool).
2. In SSH Keys, check one or more keys.
3. Some images require at least one key before create is allowed.
4. After the VM is running, connect with your matching private key:

ssh -i ~/.ssh/id_ed25519 user@<vm-public-ip>

The default username depends on the image (often shown in connection details or image docs).

Windows and firewall appliances

Windows guests do not use SSH keys in the wizard. Set the guest password instead and use the appropriate remote access method for that OS.

Firewall appliance templates (pfSense, OPNsense) also skip SSH-key inject — there is no cloud-init. Log in from the Web Console with the vendor default account. See Firewall appliance templates (pfSense and OPNsense).

Tips

• Prefer one key per person or workstation so you can revoke access cleanly.
• You cannot inject new SSH keys into an already-built VM from this screen — plan keys at create time, or configure users inside the guest later.
• Lost private key? Add a new public key for future VMs; for an existing VM use the web console (see Start, stop, reset, and open the console) to repair access.

Still stuck?

Open a support ticket from Support → Tickets if a required-key image rejects valid keys or cloud-init never installs the key on first boot.