Manage SSH Keys

Virtual Machines uses account-level SSH public keys for instance access control. Keys are referenced during provisioning and reused across instances.

Key model

Each key record includes:

• Key name
• Public key material

Supported key operations

• Create key
• Rename key
• Set key as default
• Delete key

Key validation and assignment

DC2 validates public key format on creation. Supported formats include commonly used SSH key types such as RSA and Ed25519.

During instance launch, one account key is assigned for initial SSH access. If a default key is set, it's automatically preselected for new launches.

Generating a new SSH key

If you don't have an SSH key yet, generate one locally:

ssh-keygen -t ed25519 -C "your-email@example.com"

This creates two files: id_ed25519 (private key—keep secure) and id_ed25519.pub (public key—upload to DCP).

For RSA keys (alternative):

ssh-keygen -t rsa -b 4096 -C "your-email@example.com"

Adding a public key to your account

1. Generate or locate your public key (ends with .pub)
2. Open the public key file and copy the entire content
3. In DCP Console, go to Compute → SSH Keys
4. Click "Add Key" and paste the public key material
5. Give the key a descriptive name
6. Save and verify the fingerprint matches your local key

Never upload your private key (the file without .pub extension).

Key naming conventions

Use clear, descriptive names to distinguish keys:

• laptop-macos-2026 — Laptop-specific key
• ci-cd-pipeline — Automated deployment key
• contractor-john-2026 — Temporary external access
• dev-team-shared — Team development key (if using shared key)

Tip: Set a default key

Setting a default key simplifies instance launches—it will be pre-selected in the launch dialog for new instances.

Next steps

• Launch an Instance
• Connect with SSH