> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/pam/pam-with-devolutions-server/providers/managed-providers/ssh-key-provider.md).

# SSH key provider

SSH key managed providers securely store SSH keys in Devolutions Server for account discovery, password rotation, and Remote Desktop Manager sessions.

SSH key managed providers are used to securely store SSH keys, which can then be used for account discovery or to achieve password rotation. These SSH keys can be accessed by Remote Desktop Manager for various SSH entries and sessions.

### General

| OPTION          | DESCRIPTION                           |
| --------------- | ------------------------------------- |
| **Name**        | Display name of the provider.         |
| **Description** | Optional description of the provider. |

### Host

| OPTION            | DESCRIPTION                                            |
| ----------------- | ------------------------------------------------------ |
| **Host**          | IP address or hostname where SSH key is located.       |
| **Port**          | Set the port number used to communicate with the host. |
| **Timeout (sec)** | Set a timeout for communication with the host.         |

### Credentials

| OPTION              | DESCRIPTION                                                |
| ------------------- | ---------------------------------------------------------- |
| **Credential type** | ***Custom credential*** or ***Linked credential*** option. |
| **Username**        | Username of the SSH key account.                           |
| **Password**        | Password of the SSH key account.                           |

### See also

* [Devolutions Academy – Centralize SSH key rotation with Devolutions PAM](https://academy.devolutions.net/student/activity/3039494-centralize-ssh-key-rotation-with-devolutions-pam)


---

# 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.devolutions.net/pam/pam-with-devolutions-server/providers/managed-providers/ssh-key-provider.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.