SSH keypairs are a way to authenticate to your Linux virtual machine without using a password with the added security of SSH Public-Key authentication.
Public-Key authentication is both:
Secure: breaking an SSH key requires so much time and computational power that these sorts of attacks are not practical in the real world. SSH keys are much, much secure than even very strong passwords.
Convenient: instead of managing per-machine passwords or sharing them across your company, every physical person who needs access to your servers give you their public key. You can then setup granular access control by adding those keys only to the relevant machines. If you need to revoke someone’s access, simply revoking their key prevents them from logging in without altering other people’s workflow.
Exoscale allows you to automatically provision Linux machines with SSH public keys to use for Public-Key authentication with SSHv2.
Note that while you can have multiple keypairs in your account, the instance creation dialog only allows you to select one keypair. Once the instance is created, you may allow additional public keys and set up more detailed access control using traditional means.
Keypairs can be imported or created through the keypairs view.
Importing an existing public key
Enter the New SSH keypair screen and choose IMPORT. You can then paste in the content of your public key.
Creating a new SSH keypair
If you dont’t have an SSH keypair you can choose to either create one through a simple command on your Linux machine or to create one through the Exoscale console.
Creating a new SSH keypair on your machine
You can create a new SSH keypair with the following command:
ssh-keygen -t rsa -b 4096 -C 'a-comment-to-identify-your-key'
You will be asked for a name and location to save your new keypair (keyairs are usually stored in
~/.ssh, and the main keypair for a user is usually called
id_rsa) and for a password to protect it. You can then copy and paste the content of your freshly created public key in the import text field of the New SSH keypair screen.
Creating a new SSH keypair through the Exoscale console
Access the New SSH keypair screen and choose CREATE. through this screen you will create a new SSH keypair: the public key will be available through the interface to provision your instances, while the private key will be displayed to you at the end of the process.
Saving the newly created keypair to your computer
Copy the content of the private key.
SSH keys are usually stored in the
.ssh/ in your home directory. If you don’t have the
.ssh folder you may need to create it manually with the right permissions:
mkdir -p ~/.ssh && chmod u=rwx,go-rwx ~/.ssh
You can then paste the content of your private key in a file inside your
.ssh/ folder. If you are not familiar with SSH we suggest you to name the file
id_rsa. This file as well needs specific permissions. You can create a file with the right permissions with the following command:
touch ~/.ssh/id_rsa && chmod u=rw,go-rwx ~/.ssh/id_rsa
If you wish you may extract the public key from the private key using the
ssh-keygen -y command:
ssh-keygen -y > ~/.ssh/id_rsa.pub
Finally we strongly recommend you to protect your private key with a good password:
Provisioning an instance with a keypair
When creating a new virtual machine, simply select the keypair you want to be associated to that instance and the person holding the corresponding private key will be able to log in via password-less SSH.
Plese be aware that deleting a public key in the Exoscale console does not automatically remove the authorized public key from an already created instance. If you want to completely revoke a key, you need to do so manually by deleting the key on every instance holding it.
Connecting to your newly created instance
Once your new instance has started and is running, you can connect to it via SSH. How to use SSH is out of the scope of this documentation, but assuming the following conditions:
- You have SSH installed on your machine
- Your private key is stored in
- Permissions of the
~/.sshfolder (700) and of your private key (600) are correct
- You opened TCP port 22 in your machine’s security groups
you should then be able to connect to your machine simply with:
You may be asked the password of your private key if set (not the password of your instance).
You may also see a warning about the remote host identification: this is to be expected on a first connection and you can trust the remote.