hyperpod-ssm
Remote command execution and file transfer on SageMaker HyperPod cluster nodes via AWS Systems Manager (SSM). This is the primary interface for accessing HyperPod nodes — direct SSH is not available. Use when any skill, workflow, or user request needs to execute commands on cluster nodes, upload files to nodes, read/download files from nodes, run diagnostics, install packages, or perform any operation requiring shell access to HyperPod instances. Other HyperPod skills depend on this skill for all node-level operations.
Install
With your agent
Install OMGSkills skill "awslabs/agent-plugins:plugins/sagemaker-ai/skills/hyperpod-ssm" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/awslabs/agent-plugins /tmp/agent-plugins && ln -s /tmp/agent-plugins/plugins/sagemaker-ai/skills/hyperpod-ssm ~/.claude/skills/hyperpod-ssmFrom README
HyperPod SSM Access Prerequisites aws CLI v2, authenticated for the target account/Region. session-manager-plugin — installed alongside the AWS CLI. jq — the scripts build JSON payloads with it. 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. with sudo yum expect, sudo apt expect, or brew expect. ssm-exec.sh detects and uses it automatically; falls back with a warning if missing. SSM Target Format Target: sagemaker-cluster: - CLUSTERID: Last segment of cluster ARN (NOT the cluster name). Extract via get-cluster-info.sh. GROUPNAME: Instance group name — retrieve via list-nodes.sh. INSTANCEID: EC2 instance ID (e.g., i-0123456789abcdef0) Scripts Three scripts under scripts/. Resolve cluster info and nodes once, then execute per node.
More from this repo
amplify-workflow
Used to build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first).
api-gateway
Build, manage, and operate APIs with Amazon API Gateway (REST, HTTP, and WebSocket).
aws-lambda
Design, build, deploy, test, and debug serverless applications with AWS Lambda.