Skip to main content
The SSH Keys page provides comprehensive tools for managing your credentials throughout their lifecycle, from creation to deletion.

​
Viewing and Organizing Keys

​
Key Information Display

Key Details

Essential Information
  • View key name, fingerprint, and creation date
  • Access the full public key content
  • Copy public keys to clipboard with one click
  • View regional distribution of keys

Organization Features

Management Tools
  • Search keys by name
  • Filter keys by region
  • Sort by name or creation date
  • Paginated view for large key collections

​
Key Information Components

  • Basic Information
  • Technical Details
  • Usage Information
Core Key Details
  • Key Name: User-defined identifier
  • Key Type: RSA, Ed25519, or ECDSA
  • Key Size: Bit length for security assessment
  • Creation Date: When key was added to account
  • Source: Whether created or imported

​
Deleting SSH Keys

To remove an SSH key from your account:
1

Navigate to Key Management

Navigate to the SSH Keys page
2

Locate Target Key

Find the key you want to delete using search or filters
3

Initiate Deletion

Click the “Delete” button on the key card
4

Confirm Deletion

Confirm the deletion in the popup dialog
5

Verify Removal

The key will be immediately removed from all regions

​
Key Deletion Considerations

Important Deletion Factors:
  • Irreversible: Deleted keys cannot be recovered - this action is permanent
  • VM Access Impact: You cannot delete keys that are currently in use by active VMs
  • Backup Requirement: Ensure you have at least one working SSH key before deleting others
  • Global Removal: Keys are removed from all regions simultaneously
  • Access Loss: VMs using deleted keys will lose SSH access until a new key is configured

​
Pre-Deletion Checklist

Check VM Dependencies
  • Identify all VMs using the key
  • Ensure alternative access methods exist
  • Plan for key replacement on affected VMs
  • Test alternative keys before deletion
Maintain SSH Access
  • Verify at least one other working key exists
  • Test alternative keys with existing VMs
  • Ensure team members have alternative access
  • Plan for emergency access if needed
Update Documentation
  • Remove references to deleted key from documentation
  • Update team access procedures
  • Modify automation scripts using the key
  • Update key inventory and management records

​
Using SSH Keys with Virtual Machines

SSH keys are automatically integrated into the VM deployment process:

​
VM Deployment Integration

1

Key Selection

In the SSH Key Configuration section of VM deployment, select from your available keys
2

Multi-Key Selection

Multiple keys can be selected for a single VM to allow access by different team members
3

Automatic Installation

Selected keys are automatically installed on the VM during provisioning
4

User Configuration

Keys are configured for the default user account (ubuntu, centos, etc. depending on OS)

​
Connection Examples

Basic SSH Connection: 
ssh -i /path/to/private_key username@vm_ip_address
Parameter explanations:
  • /path/to/private_key - Path to your downloaded private key file
  • username - Default user for your OS (ubuntu, centos, admin, etc.)
  • vm_ip_address - Public IP address of your VM
SSH Config File (Recommended): For easier connections, add entries to your SSH config file (~/.ssh/config): 
Host my-vm
  HostName 203.0.113.1
  User ubuntu
  IdentityFile ~/.ssh/my_private_key.pem
  IdentitiesOnly yes
After adding this configuration, you can connect simply with: ssh my-vm

​
Regional Key Distribution

SSH keys are automatically distributed across all available regions when created or imported:

​
Regional Availability

Norway Region

NORWAY-1
  • European data center
  • GDPR compliant
  • Low latency for European users

Canada Region

CANADA-1
  • North American data center
  • Privacy-focused
  • Optimized for Canadian/northern US users

US Region

US-1
  • United States data center
  • US data residency
  • Low latency for US users

​
Cross-Region Benefits

Automatic Availability
  • Keys work in all regions without manual distribution
  • Deploy VMs in any region with existing keys
  • No additional configuration required
  • Consistent access across global infrastructure
Business Continuity
  • Keys available for emergency deployments
  • Cross-region failover capabilities
  • Consistent access during regional outages
  • Simplified multi-region architecture

​
SSH Key Best Practices

​
Security Best Practices

1

Key Generation

  • Generate separate keys for different projects or environments
  • Use descriptive names that identify the key’s purpose
  • Prefer Ed25519 keys for new generations (more secure and faster)
  • Use minimum 2048-bit RSA keys (4096-bit recommended for high security)
2

Key Storage

  • Store private keys securely and never share them
  • Use passphrase protection for your private keys
  • Back up private keys in encrypted storage
  • Set correct file permissions (600 for private keys)
3

Key Maintenance

  • Regularly audit and rotate your SSH keys
  • Remove unused or unnecessary keys promptly
  • Monitor key usage and access patterns
  • Keep an inventory of where keys are deployed
4

Access Control

  • Use separate keys for different team members
  • Implement key rotation policies
  • Revoke access immediately when team members leave
  • Consider using SSH certificates for large teams

​
Operational Best Practices

Systematic Key Management
  • Use consistent naming conventions
  • Group keys by project, environment, or team
  • Document key purposes and usage
  • Maintain key inventory and ownership records
Key Lifecycle Planning
  • Plan key rotation schedules
  • Establish key retirement procedures
  • Monitor key age and usage patterns
  • Implement automated key management where possible
Multi-User Key Management
  • Establish team key management policies
  • Provide key management training
  • Implement approval processes for key changes
  • Maintain emergency access procedures

​
Troubleshooting Common Issues

​
Connection Problems

  • Permission Denied
  • Connection Refused
  • Key Not Found
SSH Authentication FailuresCommon Causes:
  • Wrong private key file
  • Incorrect file permissions
  • Wrong username for OS
  • Key not installed on VM
Solutions:
  • Verify correct private key file path
  • Set permissions: chmod 600 ~/.ssh/private_key.pem
  • Use correct username (ubuntu, centos, etc.)
  • Check key was selected during VM deployment

​
Key Management Issues

Key Deletion Blocked
  • Cause: Key is in use by active VMs
  • Solution: Remove key from VMs first or ensure alternative access
  • Prevention: Plan key replacement before deletion
  • Verification: Check which VMs are using the key
Authentication Failures
  • Cause: Key format issues or corruption
  • Solution: Re-import key or create new key
  • Prevention: Validate key format during import
  • Verification: Test key with new VM deployment
Private Key Recovery
  • Cause: Private key file deleted or corrupted
  • Solution: Cannot recover - must create new key pair
  • Prevention: Maintain secure backups of private keys
  • Mitigation: Use multiple keys for redundant access

​
Advanced Key Management

​
Key Rotation Strategy

1

Plan Rotation Schedule

  • Determine rotation frequency based on security requirements
  • Identify high-priority keys requiring frequent rotation
  • Plan rotation windows to minimize service disruption
  • Coordinate with team schedules and maintenance windows
2

Prepare New Keys

  • Generate or import new SSH keys
  • Test new keys with development VMs
  • Update team access and documentation
  • Prepare deployment procedures
3

Deploy New Keys

  • Add new keys to existing VMs
  • Verify new key functionality
  • Update automation and scripts
  • Train team on new key usage
4

Retire Old Keys

  • Remove old keys from VMs
  • Delete old keys from account
  • Update documentation and procedures
  • Verify no remaining dependencies

​
Automation Integration

Infrastructure as Code

Automated Key Management
  • Include SSH key management in infrastructure automation
  • Use configuration management tools for key deployment
  • Implement automated key rotation procedures
  • Monitor key usage and compliance

CI/CD Integration

Pipeline Integration
  • Integrate key management with deployment pipelines
  • Automate key distribution to new VMs
  • Implement automated testing of key functionality
  • Monitor and alert on key-related issues
Regular SSH key management, including monitoring usage, rotating keys, and maintaining proper access controls, is essential for maintaining the security and reliability of your virtual machine infrastructure.
Pro Tip: Maintain at least two working SSH keys at all times and test them regularly. This provides redundancy and ensures you never lose access to your VMs due to key issues.
⌘I