Cloud Shell
Cloud Shell gives you a browser-based terminal on cluster compute. It's the fastest way to get a shell on a GPU node — no SSH keys, no local client, just a tab.
Creating a Cloud Shell
Click New Cloud Shell on the Cloud Shell list page. The creation dialog asks for:
| Field | Required | What it does |
|---|---|---|
| Name | optional | Display name. Auto-generated if omitted. |
| Compute pool | required | Which compute pool to run on. Only pools tagged for cloud-shell workloads appear. |
| Slurm cluster | optional | Attach a Slurm cluster for job submission from the shell. |
Advanced options
| Field | Required | What it does |
|---|---|---|
| Image version | optional | Override the default ttyd image. |
| CPU request / limit | optional | Custom CPU allocation. |
| Memory request / limit | optional | Custom memory allocation. |
Using a Cloud Shell
Once the status flips to Running, click Open to launch the terminal in an embedded iframe. The shell is a full Linux environment with:
- Your workspace's storage mounted automatically.
- Optional Slurm integration for submitting batch jobs.
- Persistent home directory across pause/resume cycles.
Lifecycle
| Action | Effect |
|---|---|
| Open | Launch the terminal in the browser. |
| Delete | Tear down the shell and its storage. Irreversible. |
Cloud Shells are lightweight user services — they don't have a pause/resume cycle. If you're done, delete the shell and recreate it later.
Cost
Cloud Shells consume compute from your workspace's quota. The list view shows the cost estimate per shell. Shells left running on GPU nodes are the most common source of idle spend — delete them when you're not actively using them.