Import existing SSH keys from GitHub, GitLab, or other services
If you already have SSH keys that you use for other services (GitHub, GitLab, other cloud providers), you can import the public key to use with your virtual machines on our platform.
To import an existing SSH public key:
Navigate to SSH Keys
Navigate to the SSH Keys page from the sidebar
Initiate Import
Click “Import Key” button
Name Your Key
Enter a descriptive name for the key (maximum 50 characters):
Paste Public Key
Paste your public key content in the text area:
Import Key
Click “Import Key” to add it to your account:
Locate your existing public key on your system:
Common Public Key Locations
Your public key is typically located at:
Display and copy your public key:
Common Public Key Locations
Your public key is typically located at:
Display and copy your public key:
Windows Key Locations
With Git Bash or WSL:
Display with Git Bash:
With PowerShell:
Common Windows locations:
C:\Users\YourUsername\.ssh\id_rsa.pub
C:\Users\YourUsername\.ssh\id_ed25519.pub
Understanding the correct format for import:
Public Key Requirements:
A valid public key must:
ssh-rsa
, ssh-ed25519
, or ssh-dss
The platform supports industry-standard SSH key types:
RSA Key Support
RSA Key Support
Ed25519 Key Support
ECDSA Key Support
Access GitHub SSH Keys
Go to GitHub → Settings → SSH and GPG keys
Copy Public Key
Copy the public key content from GitHub
Import to Platform
Paste the key in the import dialog
Use Descriptive Name
Name it something like “github-personal-key”
Access GitLab SSH Keys
Go to GitLab → User Settings → SSH Keys
Copy Public Key
Copy the public key content from GitLab
Import to Platform
Paste the key in the import dialog
Use Descriptive Name
Name it something like “gitlab-work-key”
Format Errors
Invalid Key Format
Key Type Issues
Unsupported Key Types
Duplicate Keys
Key Already Exists
Name Conflicts
Duplicate Key Names
Security Considerations
Key Organization
Identify Source
Include the source service or system in the name
Specify Purpose
Indicate what the key will be used for
Add Context
Include environment or project information
Use Consistent Format
Develop naming convention for consistency
Example naming patterns:
github-personal-2024
gitlab-work-project-alpha
laptop-development-key
ci-cd-deployment-key
Simplified Management
Key Management Advantages
Proven Security
Using Existing Keys
Security Reminders:
Key Format Problems
Common Problems:
Solutions:
Key Format Problems
Common Problems:
Solutions:
Copy-Paste Problems
Common Problems:
Solutions:
Verify Import Success
Check that key appears in SSH keys list
Test with VM Deployment
Use imported key for new VM deployment
Test SSH Connection
Connect to VM using imported key
Validate Functionality
Confirm normal SSH operations work correctly
Import Existing Keys When:
Import Existing Keys When:
Create New Keys When:
Importing existing SSH keys allows you to use your established keys while keeping your private key secure on your local machine. This is often the preferred method for users who already have a key management system in place.
When importing keys from services like GitHub or GitLab, use descriptive names that indicate both the source and purpose. This makes it easier to manage multiple keys and understand their intended use.
Import existing SSH keys from GitHub, GitLab, or other services
If you already have SSH keys that you use for other services (GitHub, GitLab, other cloud providers), you can import the public key to use with your virtual machines on our platform.
To import an existing SSH public key:
Navigate to SSH Keys
Navigate to the SSH Keys page from the sidebar
Initiate Import
Click “Import Key” button
Name Your Key
Enter a descriptive name for the key (maximum 50 characters):
Paste Public Key
Paste your public key content in the text area:
Import Key
Click “Import Key” to add it to your account:
Locate your existing public key on your system:
Common Public Key Locations
Your public key is typically located at:
Display and copy your public key:
Common Public Key Locations
Your public key is typically located at:
Display and copy your public key:
Windows Key Locations
With Git Bash or WSL:
Display with Git Bash:
With PowerShell:
Common Windows locations:
C:\Users\YourUsername\.ssh\id_rsa.pub
C:\Users\YourUsername\.ssh\id_ed25519.pub
Understanding the correct format for import:
Public Key Requirements:
A valid public key must:
ssh-rsa
, ssh-ed25519
, or ssh-dss
The platform supports industry-standard SSH key types:
RSA Key Support
RSA Key Support
Ed25519 Key Support
ECDSA Key Support
Access GitHub SSH Keys
Go to GitHub → Settings → SSH and GPG keys
Copy Public Key
Copy the public key content from GitHub
Import to Platform
Paste the key in the import dialog
Use Descriptive Name
Name it something like “github-personal-key”
Access GitLab SSH Keys
Go to GitLab → User Settings → SSH Keys
Copy Public Key
Copy the public key content from GitLab
Import to Platform
Paste the key in the import dialog
Use Descriptive Name
Name it something like “gitlab-work-key”
Format Errors
Invalid Key Format
Key Type Issues
Unsupported Key Types
Duplicate Keys
Key Already Exists
Name Conflicts
Duplicate Key Names
Security Considerations
Key Organization
Identify Source
Include the source service or system in the name
Specify Purpose
Indicate what the key will be used for
Add Context
Include environment or project information
Use Consistent Format
Develop naming convention for consistency
Example naming patterns:
github-personal-2024
gitlab-work-project-alpha
laptop-development-key
ci-cd-deployment-key
Simplified Management
Key Management Advantages
Proven Security
Using Existing Keys
Security Reminders:
Key Format Problems
Common Problems:
Solutions:
Key Format Problems
Common Problems:
Solutions:
Copy-Paste Problems
Common Problems:
Solutions:
Verify Import Success
Check that key appears in SSH keys list
Test with VM Deployment
Use imported key for new VM deployment
Test SSH Connection
Connect to VM using imported key
Validate Functionality
Confirm normal SSH operations work correctly
Import Existing Keys When:
Import Existing Keys When:
Create New Keys When:
Importing existing SSH keys allows you to use your established keys while keeping your private key secure on your local machine. This is often the preferred method for users who already have a key management system in place.
When importing keys from services like GitHub or GitLab, use descriptive names that indicate both the source and purpose. This makes it easier to manage multiple keys and understand their intended use.