Hyperpod Issue Report

When your HyperPod cluster starts acting up and you need to collect diagnostics for AWS Support, this automates the tedious work of SSM-ing into nodes and gathering logs. It works with both EKS and Slurm orchestrators, auto-detects cluster type, and runs collection in parallel across nodes. You point it at your cluster and an S3 bucket, and it pulls system logs, configurations, and custom command output into a structured report. The workflow is straightforward: gather cluster details, verify your AWS permissions, run the bundled Python script via uv, then download or analyze results. Honest take: this is really just plumbing around AWS APIs and SSM sessions, but that plumbing saves hours when you're troubleshooting production issues at 2am.

skills.sh installs: 147
GitHub stars: 938
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add awslabs/agent-plugins --skill hyperpod-issue-report --agent claude-code

Installs into .claude/skills of the current project.

Files

HyperPod Issue Report

Collect diagnostic logs from HyperPod cluster nodes via SSM, store results in S3. Supports both EKS and Slurm clusters with auto-detection. Uses the bundled scripts/hyperpod_issue_report.py for reliable parallel collection.

Prerequisites

AWS CLI configured with permissions: sagemaker:DescribeCluster, sagemaker:ListClusterNodes, ssm:StartSession, s3:PutObject, s3:GetObject, eks:DescribeCluster
Python 3.8+ and uv (see uv installation docs for install options)
SSM Agent running on target nodes; node IAM roles need s3:GetObject/s3:PutObject on the report bucket
For EKS clusters: kubectl installed and configured (see Workflow step 2)