Configure SSH keys for secure access to your virtual machines
SSH keys provide secure access to your virtual machines. SSH key management requires user authentication.
SSH Key Prerequisites:
Access your SSH keys through the platform interface:
Seamless Integration
Flexible Key Assignment
Generate new SSH key pairs directly through the platform interface.
Access SSH Keys
Navigate to SSH Keys section
Initiate Creation
Click “Create Key” in the SSH key management interface
Name Your Key
Enter a unique name for the key (1-50 characters):
Generate and Download
Click “Create Key” to generate the keypair:
Automatic Generation
Secure Key Creation
Instant Download
Secure Key Delivery
Platform Integration
Seamless Platform Integration
Private Key Security:
• The private key is only available for download once during creation • Store it securely as it cannot be retrieved later from our servers • The private key file is automatically downloaded for security reasons • Never share your private key with anyone or upload it to version control • Back up your private key in a secure location
Import SSH keys that you already use for other services.
Access Import Function
Navigate to SSH Keys and click “Import Key”
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:
Valid public key requirements:
ssh-rsa
, ssh-ed25519
, or ssh-dss
After downloading your private key file, you must set the correct permissions for security:
Set Secure Permissions
Example:
This command ensures only you can read and write the file, which is required for SSH security.
Set Secure Permissions
Example:
This command ensures only you can read and write the file, which is required for SSH security.
PowerShell Permission Setting
Example:
This removes inheritance and grants only the current user read/write access.
Account Restrictions
Key Naming Rules
The platform supports industry-standard SSH key types:
RSA Keys
RSA Key Support
Ed25519 Keys
Ed25519 Key Support
ECDSA Keys
ECDSA Key Support
Once your keys are configured, use them to connect to your VMs:
Parameter explanations:
/path/to/private_key
- Path to your downloaded private key fileusername
- Default user for your OS (ubuntu, centos, admin, etc.)vm_ip_address
- Public IP address of your VMDefault Username: ubuntu
All Ubuntu-based OS images use the ubuntu
user by default.
Default Username: ubuntu
All Ubuntu-based OS images use the ubuntu
user by default.
Common Default Usernames
For easier connections, add entries to your SSH config file (~/.ssh/config
):
After adding this configuration, you can connect simply with:
During VM deployment, you can configure SSH key access:
Automatic Selection
If you have only one SSH key, it’s automatically selected
Manual Selection
If you have multiple keys, choose the appropriate one for the VM
Key Validation
System validates key availability and format
VM Integration
Selected keys are automatically installed on the VM during provisioning
Multiple Key Benefits
Redundant Access
SSH keys are automatically distributed across all available regions when created or imported:
Seamless Regional Access
Seamless Regional Access
Regional Coverage
All keys work in all regions automatically.
Key Generation
Secure Key Creation
Key Storage
Secure Key Management
Key Maintenance
Ongoing Key Management
Access Control
Team Key Management
Plan Key Strategy
Implement Key Management
Monitor and Maintain
Scale Security
Use descriptive key names that indicate their purpose, such as “production-web-servers” or “ml-development-team”, to make key management easier as your infrastructure grows.
Configure SSH keys for secure access to your virtual machines
SSH keys provide secure access to your virtual machines. SSH key management requires user authentication.
SSH Key Prerequisites:
Access your SSH keys through the platform interface:
Seamless Integration
Flexible Key Assignment
Generate new SSH key pairs directly through the platform interface.
Access SSH Keys
Navigate to SSH Keys section
Initiate Creation
Click “Create Key” in the SSH key management interface
Name Your Key
Enter a unique name for the key (1-50 characters):
Generate and Download
Click “Create Key” to generate the keypair:
Automatic Generation
Secure Key Creation
Instant Download
Secure Key Delivery
Platform Integration
Seamless Platform Integration
Private Key Security:
• The private key is only available for download once during creation • Store it securely as it cannot be retrieved later from our servers • The private key file is automatically downloaded for security reasons • Never share your private key with anyone or upload it to version control • Back up your private key in a secure location
Import SSH keys that you already use for other services.
Access Import Function
Navigate to SSH Keys and click “Import Key”
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:
Valid public key requirements:
ssh-rsa
, ssh-ed25519
, or ssh-dss
After downloading your private key file, you must set the correct permissions for security:
Set Secure Permissions
Example:
This command ensures only you can read and write the file, which is required for SSH security.
Set Secure Permissions
Example:
This command ensures only you can read and write the file, which is required for SSH security.
PowerShell Permission Setting
Example:
This removes inheritance and grants only the current user read/write access.
Account Restrictions
Key Naming Rules
The platform supports industry-standard SSH key types:
RSA Keys
RSA Key Support
Ed25519 Keys
Ed25519 Key Support
ECDSA Keys
ECDSA Key Support
Once your keys are configured, use them to connect to your VMs:
Parameter explanations:
/path/to/private_key
- Path to your downloaded private key fileusername
- Default user for your OS (ubuntu, centos, admin, etc.)vm_ip_address
- Public IP address of your VMDefault Username: ubuntu
All Ubuntu-based OS images use the ubuntu
user by default.
Default Username: ubuntu
All Ubuntu-based OS images use the ubuntu
user by default.
Common Default Usernames
For easier connections, add entries to your SSH config file (~/.ssh/config
):
After adding this configuration, you can connect simply with:
During VM deployment, you can configure SSH key access:
Automatic Selection
If you have only one SSH key, it’s automatically selected
Manual Selection
If you have multiple keys, choose the appropriate one for the VM
Key Validation
System validates key availability and format
VM Integration
Selected keys are automatically installed on the VM during provisioning
Multiple Key Benefits
Redundant Access
SSH keys are automatically distributed across all available regions when created or imported:
Seamless Regional Access
Seamless Regional Access
Regional Coverage
All keys work in all regions automatically.
Key Generation
Secure Key Creation
Key Storage
Secure Key Management
Key Maintenance
Ongoing Key Management
Access Control
Team Key Management
Plan Key Strategy
Implement Key Management
Monitor and Maintain
Scale Security
Use descriptive key names that indicate their purpose, such as “production-web-servers” or “ml-development-team”, to make key management easier as your infrastructure grows.