> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scitix.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage Key Pairs

> Learn how to create, import, and delete key pairs, and review security considerations for using key pairs to log in to CES instances.

Key Pairs are used to log in to CES instances through SSH. When creating an instance, if you select **Key Pair**, you must first prepare an available key pair.

A key pair consists of a public key and a private key. The platform stores the public key, while users are responsible for storing the private key. When a key pair is generated automatically, the private key file is available for download only once. Please save it to a secure location immediately.

## Usage Recommendations

* When centralized management of login credentials is required to reduce the risk of password exposure, we recommend using Key Pair login.
* In shared environments, do not share the same private key file among multiple users. Manage access credentials separately by user or operational process.
* Do not upload private key files to public code repositories, images, script templates, ticket attachments, or logs.
* If a private key is compromised, we recommend deleting the corresponding Key Pairs and changing the access method for instances that use the Key Pair for login.

## Create Key Pairs

1. Log in to the [GPU Cloud console](https://console.scitix.ai/gpu-cloud/home) and go to the **Instance** page.

2. Click the **Key Pairs** tab, then click **Create Key Pair**.

3. Enter a name.

4. Select **Creation Method**.

   | Parameter | Description |
   | - | - |
   | **Automatic Creation** | The system automatically generates a key pair and provides a one-time download of the private key file (`.pem`). Keep the private key secure, as the platform does not retain a copy. |
   | **Import Public Key** | Create a key pair using an existing SSH public key. This is suitable when you have already generated a key pair locally or in another system and only need to import the public key to the platform. |

5. If you select **Import Public Key**, paste the prepared SSH public key content.

6. Click **Confirm**.

After creation is complete, confirm that the Key Pairs have been created. When using **Auto Create**, immediately download and save the private key file.

## Delete Key Pairs

### Confirm Before Deletion

* It has been confirmed that this key pair is no longer needed to log in to newly created CES instances.
* It has been confirmed whether any instances or O\&M processes still depend on this key pair.
* If the key pair needs to be deleted due to exposure, also check the access methods of instances that use this key pair.

### Deletion Steps

1. On the **Key Pairs** tab, locate the key pair to delete.

2. Click **Delete**.

3. In the confirmation dialog, verify the Key Pairs information and confirm the deletion.

After you delete a key pair, it can no longer be selected when creating instances. The platform will not automatically delete saved private key files. Handle them in accordance with your internal security requirements.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.