hyperpod-ssm

1# HyperPod SSM Access
2 
3## Prerequisites
4 
5- **`aws` CLI v2**, authenticated for the target account/Region.
6- **`session-manager-plugin`** — installed alongside the AWS CLI.
7- **`jq`** — the scripts build JSON payloads with it.
8- **`unbuffer`** (from the `expect` package) — wraps `aws ssm start-session` with a PTY so the session-manager-plugin flushes stdout instead of racing to close. Without it, calls intermittently return empty output with `Cannot perform start session: EOF` even when the command ran. Install with `sudo yum install expect`, `sudo apt install expect`, or `brew install expect`. `ssm-exec.sh` detects and uses it automatically; falls back with a warning if missing.
9 
10## SSM Target Format
11 
12Target: `sagemaker-cluster:<CLUSTER_ID>_<GROUP_NAME>-<INSTANCE_ID>`
13 
14- `CLUSTER_ID`: Last segment of cluster ARN (NOT the cluster name). Extract via `get-cluster-info.sh`.
15- `GROUP_NAME`: Instance group name — retrieve via `list-nodes.sh`.
16- `INSTANCE_ID`: EC2 instance ID (e.g., `i-0123456789abcdef0`)
17 
18## Scripts
19 
20Three scripts under `scripts/`. Resolve cluster info and nodes **once**, then execute per node.
21 
22### get-cluster-info.sh — Resolve cluster name → ID (call once)
23 
24```bash
25scripts/get-cluster-info.sh CLUSTER_NAME [--region REGION]
26# Output: {"cluster_id":"...","cluster_arn":"...","cluster_name":"...","region":"..."}
27```
28 
29### list-nodes.sh — List all nodes with pagination (call once)
30 
31```bash
32…