SSH Keys
An SSH key is a pair of matching files that lets you log in to a Linux VM without typing a password. The public key goes on the VM; the private key stays on your computer and proves it’s you. Think of the public key as a lock you fit on the server and the private key as the only key that opens it.
You save public keys in the portal once, then pick them when you deploy a VM. IBEE puts the selected public keys on the VM when it is created.
Choose how to log in
Saved SSH keys are personal: the list shows the keys you saved in the current workspace. Teammates don’t see your keys, and you don’t see theirs.
How it works
- You create a key pair in the portal (it downloads the private key), or you import the public key of a pair you already have.
- When you deploy a Linux VM, you select one or more saved keys.
- You connect with
sshand your private key.
Before you begin
- Write access to the workspace: the Owner, an Admin, or a Technical member with access to it. Collaborators can only view. See Team members & access roles.
- Identity verification, to create, import or delete keys. See Verify your identity.
- To import a key: the public key file from your computer, usually
~/.ssh/id_ed25519.pub. Never upload the private key. - An SSH client. macOS, Linux and Windows 10 or later include
sshin the terminal.
Create a key pair in the portal
Use this when you don’t have a key yet.
The private key downloads once only. IBEE keeps only the public key and can’t send the private key again. Move the .pem file somewhere safe now. If you lose it, create a new key pair and add it to your VMs.
ssh refuses a private key that other users on your computer can read. On macOS or Linux, lock it down after downloading:
Import a key you already have
To make a new key pair on your own computer first, run this and press Enter at each prompt:
This creates ~/.ssh/id_ed25519 (private, keep it) and ~/.ssh/id_ed25519.pub (public, import this one).
Use a key when you deploy a VM
In the VM deploy form, select one or more saved keys in the SSH Keys section, or click Add Key to create or import one without leaving the form. See Create a VM.
Through the API, saved keys have no endpoints of their own: send the public key text in ssh_keys when you create a VM. See Create a VM.
Connect to the VM
On the VM’s Overview, Connection Details shows its IP address and login user. Connect with the matching private key:
Verify it worked
The first time, ssh asks you to confirm the server’s fingerprint: type yes. You then get a shell prompt on the VM without being asked for a password.
Add or remove keys on a running VM
Open a running Linux Cloud or GPU VM and go to Settings → Access. You need write access to the workspace.
- SSH keys lists the keys installed on the VM. To add one, pick a saved key in Select SSH key and click Add key. Tick Disable password login after adding this key to switch to key-only login at the same time.
- Click Remove to take a key off the VM. If password login is off, removing the last key asks Remove the last SSH key?: confirm with Remove key only if you have another way in.
- Password login shows On or Off; click Turn on or Turn off. You can turn it off only while the VM has at least one SSH key.
- Reset password: enter a New password (at least 8 characters) twice and click Reset password.
Windows VMs show a Remote Desktop section instead; manage users and passwords inside Windows.
Through the API, use PATCH /compute/cloud-vms/{vm_id}/actions/access (GPU VMs: /compute/gpu-vms/{vm_id}/actions/access) with ssh_keys and ssh_key_mode (add or remove), new_password, or password_auth_enabled.
Delete a saved key
On SSH Keys, click Delete on the key’s row, then Delete Key in Delete SSH Key.
Deleting a saved key only removes it from your list. It does not take the key off VMs that already have it, even though the dialog says servers will stop accepting it. To cut off access, remove the key from each VM under Settings → Access, or delete its line from ~/.ssh/authorized_keys on the VM.
Limits
Because each person can save a public key only once, you can’t save the same key in a second workspace. Create a separate key pair for each workspace, or pass the public key text in ssh_keys through the API.
Security tips
- Use one key pair per computer, so you can remove one laptop’s access without touching the others.
- Protect the private key with a passphrase when you run
ssh-keygen. - Once a key works, turn Password login off under Settings → Access.
- When someone leaves your team, remove their keys from each VM under Settings → Access.
Troubleshooting
Related pages
- Create a VM: pick keys at deploy time
- Launch your first VM: create, connect and clean up end to end
- Create firewall rules: allow SSH on port 22
- API Tokens: automate VM access through the API
