> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-openstack/5.4/authentication-and-authorization/authentication-ssh-key-value-generation.md).

# Create SSH Key-Value Pair with Bash

You can run the `ssh-keygen` utility on your local machine to generate an SSH key-value pair.

The `ssh-keygen` utility generates a pair comprising of a public key and private key. The private key is stored in the file `id_rsa` while the public key is stored in the file `id_rsa.pub`.

### Creating a SSH Key Value Pair

To create an SSH key value pair, follow the steps given below.

1\. Launch Bash on your machine.

{% tabs %}
{% tab title="Bash" %}

```bash
ssh-keygen -t rsa -f cloud-key
```

{% endtab %}
{% endtabs %}

2\. Run the following command to generate the SSH key.

3\. Follow the instructions in Bash to create a passphrase which is your private key.

4.Press the `Enter` key.

A public and private key are generated on running the above command.

The `cloud-key` file contains the private key and `id_rsa.pub` contains the public key.

You can copy the content of the public key file `id_rsa.pub` to generate an SSH key-value pair.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform9.com/managed-openstack/5.4/authentication-and-authorization/authentication-ssh-key-value-generation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.