Manage SSH Key

Manage SSH Key

A key pair, composed of a public key and a private key, serves as a crucial set of security credentials used to authenticate your identity when connecting to a Greennode bare-metal. Greennode securely stores the public key on your instance, while you retain control of the private key. For Linux instances, the private key enables a secure SSH connection to your instance. Alternatively, you can leverage Greennode's integrated Systems Manager Session Manager for an interactive, one-click, browser-based shell. The private key, in the possession of anyone, grants access to your instances. Therefore, it is imperative to safeguard your private key in a secure location.
​
During instance launch, you have the option to specify a key pair. If SSH connectivity is essential, a key pair must be specified. You can either select an existing key pair or generate a new one. Depending on your security strategy, you may use the same key pair across all instances or assign different key pairs. Upon the initial boot, the specified public key is placed in your Linux instance under ~/.ssh/authorized_keys. When connecting via SSH, you must provide the corresponding private key for authentication. Refer to the Connect to your Linux instance documentation for detailed connection instructions. For insights into key pairs and Windows instances, consult the Greennode Key Pairs and Windows Instances documentation.

It's vital to note that Greennode does not retain a copy of your private key, making recovery impossible in the event of loss. However, alternative methods exist for connecting to instances in the scenario of a lost private key.  Greennode facilitates the creation of key pairs, allowing you to generate them directly within the platform. Alternatively, you can employ third-party tools to create key pairs and subsequently import the public keys to Greennode

Importing an SSH Key on GreenNode

Scenarios

To ensure system security, you are advised to use the key authentication mode to authorize the user who attempts to log in to a BMS. Therefore, you must use an existing key pair or create a new one for remote login authentication.

If you store a public key by clicking Save public key of PuTTYgen, the format of the public key content will change. Such a key cannot be imported to the management console. To resolve this issue, obtain the public key content in correct format and import the content to the management console. For details, see What Do I Do If a Key Pair Created Using PuTTYgen Cannot Be Imported to the Management Console?

Procedure

  1. Access the GreenNode console.
  2. From the Platform menu, Click the Bare-metal> SSH Keys menu in that order.
  3. The SSH Keys console is displayed.
  4. On the left side of the page, click Import SSH Key.
  5. Input SSH Key name. Only letters (a-z, A-Z, 0-9, '_', '-') are allowed. Your input data length must be between 5 and 50. Must start with letter. Copy the content of the public key in .txt file into the Public Key content text box
  6. Click Import

Create a Key Pair on the Management Console

  1.  Access the GreenNode console.
  2. From the Platform menu, Click the Bare-metal> SSH Keys menu in that order.
  3. The SSH Keys console is displayed.
  4. On the left side of the page, click Create SSH Key.
  5. Enter the key name and click OK.
  6. After clicking create, the system will automatically download the private key file. The file name is the specified key pair name with a suffix of .pem. Store the private key file securely

Delete a SSH Key

Scenarios

If you no longer need a key pair, you can delete it. After a key pair is deleted, it cannot be restored. However, you can still use the private key saved locally to log in to the BMS, and the deleted key pair is still displayed in the BMS details

Procedure

  1. Access the GreenNode console.
  2. From the Platform menu, Click the Bare-metal> SSH Keys menu in that order.
  3. The SSH Keys console is displayed.
  4. Locate the row that contains the target SSH Key, click Action column, and select Delete from the drop-down list. To delete multiple SSH Key, select them and click Delete at the top of the SSH Key list.
  5. In the displayed dialog box, click Yes.

    • Related Articles

    • What Are the Key Features of Bare Metal GPU Servers?

      Bare-metal GPU Servers Key Features Direct Hardware Access: Bare-metal servers provide direct access to the underlying physical hardware without the need for a hypervisor or virtualization layer. This direct access contributes to enhanced performance ...

    • Manage VPC Network

      Create VPC Network Scenarios Creating a Virtual Private Cloud (VPC) before deploying bare-metal in a cloud environment offers many benefits. VPC helps manage network resources, provides better security, efficient IP address management, easy ...

    • Manage Bare-metal GPU Server

      Re-name a bare-metal To make it easy for you to identify and manage each Bare-metal, the cloud platform allows you to set Bare-metal names and change the names at any time. The new name of a Bare-metal takes effect after the Bare-metal is restarted. ...

    • Create Bare-metal GPU Servers

      This document describes how to create and manage bare metal servers on the GreenNode console. Access to creation page To use a Bare-Metal GPU Server, you must create a server on the GreenNode console. The following describes how to create a bare ...

    • Connect to Bare-metal

      Users have many ways to connect to the Bare-metal such as the Console function on GreenNode Portal or other client tools. Depending on the operating system of the bare-metal, the operating system of your personal computer or the desired connection ...