> For the complete documentation index, see [llms.txt](https://docs.w.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.w.ai/compute-rentals/ssh.md).

# SSH

SSH access is available for compute rentals. This feature supports all backends (CUDA, Metal, ROCM, and Vulkan), providing direct SSH connectivity to GPU machines.

**Activating SSH Access**

1. **Select SSH Options:**
   * Upon initiating your rental, choose the SSH tab.
2. **Receive Login Details:**
   * Post provisioning, the following details are available:
     * **SSH Host**: Address to connect.
     * **Username & Private Key**: Credentials for access. (Download this key as it will not be shown again after the initial display of it).
3. **Connecting via SSH:**
   * Use the provided host address and credentials to establish the SSH connection.\
     You can also use it in the Web Terminal by clicking the button "Open in Web Terminal"

**Key Features**

* **Direct Machine Access**: Provides real-time command line access.
* **Secure Tunnel**: SSH sessions are secure and encrypted.
* **Operational Flexibility**: Allows operational adjustments and in-depth system control.

#### Note

Ensure SSH access adheres to the network restrictions and use cases permitted by the w\.ai environment.


---

# 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.w.ai/compute-rentals/ssh.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.