SSH Keys in Scalr¶
Definition and Scope¶
Upon launching servers, Scalr automatically generates a new SSH Keypair and makes it available to users. These key pairs can be used to remotely log into servers. If you have different authentication methods like password auth, this can still be used, Scalr will not interfere with it. When launching a Windows server, Scalr will create a SSH key and/or a password. Some clouds require a SSH key to decrypt the Windows password.
If you do not have policy set, Scalr will automatically generate a new key per Farm. All servers within a farm will use the same key, keys can be downloaded in PEM or PPK format depending on what you need. There are two ways to access keys depending on the permissions that are set:
- Go to the Farms or Servers page in the Environment scope, find your server or farm, click on the dropdown on the right hand side , and click on Server Credentials.
- Go to the main Scalr menu dropdown on the top left and click on SSH keys. Once the SSH key page shows up, find the SSH key for your Farm and download the key:
To log into the servers with your keypair you will need to use the correct username for each cloud:
|AWS||root or a predefined username on the image.|
|scalr or the username associated with the key if a policy is used.|
|VMware||root or a predefined username on the image.|
|Openstack||root or a predefined username on the image.|
Adding Policy for Keys¶
Some organizations like to enforce policies around how users log into their servers. In this case, a policy can be created to ensure a specific key is used for ALL servers within an Environment. This key must exist in the cloud provider for it to be used by a policy. End users will not be able to download this key, it is up to the administrators to tell the users how to log into the servers.
To create a policy for SSH keys, go to the Account scope, click on the main Scalr menu , click on Policy Engine > Policy Groups. In here you can either add to an existing cloud Policy or create a new one, search for cloud.ssh.key_pair and enter the name of the key as it appears in the cloud provider:
To learn more about the Policy Engine, please go here: Policy Engine