Managing access with SSH keys

SSH keys enable a user to manage and assign RSA keys for the root user to a server at build time from the API or the Cloud Control Panel.

Key names are associated with a public and private key pair in the API and the control panel. You can create a key pair or upload an existing public key and associate it with a key name. If you create a new key pair, the private key is saved as a .pem suffixed file.

SSH keys are stored per region. For example, a key stored in the DFW region is not usable in the IAD region unless it is also added there. You can list, view, and delete SSH keys using the API or the control panel.

Note

SSH keys only work in conjunction with a server running Linux and are not compatible with Windows. Although the API will allow a Windows server to be built with a key, the key will not be functional.

See also

Using flavors to create a new cloud server Changing the characteristics of a cloud server Monitoring events on your cloud server Creating a cloud server in a region Handling host-related issues Operating a cloud server with nova-agent Configuring disks for a cloud server Managing access with SSH keys Synchronizing time with NTP Describing a cloud server with metadata: Setting and updating metadata Showing metadata

Understanding flavor classes: Flavor classes for virtual cloud servers Flavor classes for OnMetal cloud servers Choosing a flavor class Checking for regional availability of flavor classes Controlling cloud server initiation: Controlling boot behavior with cloud-init Controlling boot behavior with a config drive Controlling boot behavior with personality

Understanding Cloud Servers introduces key ideas. To learn how to put these ideas to work, start at Actions for Cloud Servers.