What Is It?
SSH Key Manager stores and manages SSH public keys for secure Linux VM access. Store up to 100 public keys, associate them with VMs during provisioning, and authenticate using key-based SSH login instead of passwords. Centralized key management across infrastructure with default key pre-selection for streamlined VM configuration.
Quick Facts
| Aspect | Details |
|---|---|
| Capacity | Up to 100 public keys per user |
| Key Type | SSH public keys (*.pub files or text) |
| Authentication | Key-based SSH login (no password required) |
| Default Key | Optional flag to pre-select key for VM configurations |
| Scope | Per-user (each user has their own SSH Keys store; not shared with other users on the same account, but usable across that user's own VDCs and VMs) |
| Supported Images | Public Linux images only |
| Management | Data Center Designer (DCD) SSH Keys view |
What You Can Do
Store Public Keys
Add public keys by name, paste key text, or upload *.pub files. Store up to 100 keys per user. Keys stored centrally and available across all VDCs.
Set Default Key
Mark a key as Default to pre-select it when configuring SSH access for new VMs. Streamlines VM provisioning by automatically suggesting preferred key. Only one default key at a time.
Associate Keys with VMs
Select stored public keys when creating or attaching Linux storage images to VMs. Multiple keys can be selected per VM during provisioning (post-provisioning additional keys must be added manually inside the VM). SSH Keys setting appears only for public Linux images during provisioning.
Note: Selected keys are injected into VM's ~/.ssh/authorized_keys file during provisioning, enabling key-based login.
Authenticate via SSH
Connect to VMs using matching private key from your workstation. No password prompt when key is correctly associated. Use standard SSH command with private key path.
Delete Keys
Remove keys from manager when no longer needed. Select key from SSH Keys view and confirm deletion. Deleted keys cannot be chosen for new VMs.
Note: Deleting a key from manager does not remove it from VMs already provisioned with that key.
Generate Key Pairs
Use ssh-keygen on workstation to create new key pairs. Accept default location or specify custom path. Optionally set passphrase for private key protection. Upload public key (id_rsa.pub) to SSH Key Manager.
Best For
| Scenario | Why It Fits |
|---|---|
| Secure Linux VM access | Key-based authentication eliminates password vulnerabilities |
| Team access management | Store team member keys centrally, associate Multiple SSH key per VM during provisioning (additional keys can be added manually inside the VM). |
| Automated provisioning | Default key pre-selection streamlines VM creation workflows |
| Development environments | Quick VM spin-up with pre-configured SSH access |
| Compliance requirements | Key-based authentication meets many security standards, eliminates password sharing |
Key Considerations
Billing & Costs
- No additional charge for SSH Key Manager
- Included with IONOS Cloud account
- No per-key fees or storage charges
Limitations
- Maximum 100 public keys per user
- Public Linux images only (not available for Windows or private images)
- Keys associated during VM provisioning (cannot add keys to running VMs via manager)
- Only public key stored in manager (private key remains on your workstation)
- Deleting key from manager does not remove it from already-provisioned VMs
- One default key at a time
- Key injection happens at provisioning time only
Management Options
- Data Center Designer (DCD) SSH Keys view
- Add Key, Delete Key, Set Default actions
- Upload *.pub file or paste key text
- Cloud API supports only ad-hoc SSH key injection at storage-volume creation; the SSH Keys store itself cannot be managed via Cloud API
- Standard SSH client for authentication (ssh -i /path/to/key.pem user@host)