hyperpod-version-checker

$npx mdskill add awslabs/agent-plugins/hyperpod-version-checker

Check and compare software component versions on SageMaker HyperPod cluster nodes.

  • Detects version mismatches across nodes for troubleshooting and upgrade planning.
  • Uses nvidia-smi, nvcc, and system package managers to query components.
  • Compares detected versions against known compatibility requirements.
  • Outputs a text report to console and file, with optional JSON for parsing.

SKILL.md

.github/skills/hyperpod-version-checkerView on GitHub ↗
---
name: hyperpod-version-checker
description: Check and compare software component versions on SageMaker HyperPod cluster nodes - NVIDIA drivers, CUDA toolkit, cuDNN, NCCL, EFA, AWS OFI NCCL, GDRCopy, MPI, Neuron SDK (Trainium/Inferentia), Python, and PyTorch. Use when checking component versions, verifying CUDA/driver compatibility, detecting version mismatches across nodes, planning upgrades, documenting cluster configuration, or troubleshooting version-related issues on HyperPod. Triggers on requests about versions, compatibility, component checks, or upgrade planning for HyperPod clusters.
metadata:
  version: "1.0.0"
---

# HyperPod Version Checker

Upload to cluster nodes via `hyperpod-ssm` skill, then execute.

## Usage

```bash
# Text report to console + file
bash hyperpod_check_versions.sh

# JSON only to stdout (text report still saved to file) — best for piping/parsing
bash hyperpod_check_versions.sh --json

# Custom output file
bash hyperpod_check_versions.sh --output /tmp/versions.txt

# No color (for logging)
bash hyperpod_check_versions.sh --no-color
```

Output file: `component_versions_<hostname>_<timestamp>.txt` (default)

## What It Checks

| Component         | Detection Method                                | Applicable When                               |
| ----------------- | ----------------------------------------------- | --------------------------------------------- |
| NVIDIA Driver     | `nvidia-smi`                                    | GPU instances (p3/p4/p5/g5)                   |
| CUDA Toolkit      | `nvcc`, `/usr/local/cuda` symlink               | GPU instances                                 |
| cuDNN             | Header file, packages                           | GPU instances doing deep learning             |
| NCCL              | Library filename, header, packages              | Distributed GPU training                      |
| EFA               | `/opt/amazon/efa_installed_packages`, `fi_info` | EFA-capable instances (p4d/p4de/p5/trn1/trn2) |
| AWS OFI NCCL      | `efa_installed_packages`, library search        | EFA + NCCL workloads                          |
| GDRCopy           | rpm/dpkg, kernel module                         | GPU instances with RDMA (p4d+/p5)             |
| MPI               | `mpirun`, `/opt/amazon/openmpi`                 | Distributed training                          |
| Neuron SDK        | `neuronx-cc`, `neuron-ls`, packages             | Trainium/Inferentia (trn1/trn2/inf1/inf2)     |
| Python/PyTorch    | `python3`, `torch` import                       | ML workloads                                  |
| Container runtime | `docker`, `containerd`, `kubectl`, `nvidia-ctk` | EKS clusters                                  |

## Multi-Node Comparison

Run on each node individually via the `hyperpod-ssm` skill. With `--json`, stdout is clean JSON for easy diffing.

## Compatibility Reference

The script automatically analyzes CUDA/driver compatibility. For reference:

| Driver Series | Supported CUDA                |
| ------------- | ----------------------------- |
| 580+          | 13.x, 12.x, 11.x              |
| 570+          | 12.8+ (Blackwell), 12.x, 11.x |
| 545+          | 12.3-12.7, 11.x               |
| 525-535       | 12.0-12.2, 11.x               |
| 450+          | 11.x only                     |

NCCL: Use 2.18+ for CUDA 12.x, 2.12+ for CUDA 11.x. Must be consistent across all nodes.

| EFA Installer | AWS OFI NCCL          |
| ------------- | --------------------- |
| 1.29+         | v1.7.3+ (recommended) |
| 1.26-1.28     | v1.7.0-v1.7.2         |
| 1.20-1.25     | v1.6.0+               |

More from awslabs/agent-plugins

SkillDescription
amazon-location-serviceIntegrates Amazon Location Service APIs for AWS applications. Use this skill when users want to add maps (interactive MapLibre or static images); geocode addresses to coordinates or reverse geocode coordinates to addresses; calculate routes, travel times, or service areas; find places and businesses through text search, nearby search, or autocomplete suggestions; retrieve detailed place information including hours, contacts, and addresses; monitor geographical boundaries with geofences; or track device locations. Covers authentication, SDK integration, and all Amazon Location Service capabilities.
amplify-workflow'Build and deploy full-stack web and mobile apps with AWS Amplify Gen2
aws-architecture-diagramGenerate validated AWS architecture diagrams as draw.io XML using official AWS4 icon libraries. Use this skill whenever the user wants to create, generate, or design AWS architecture diagrams, cloud infrastructure diagrams, or system design visuals. Also triggers for requests to visualize existing infrastructure from CloudFormation, CDK, or Terraform code. Supports two modes: analyze an existing codebase to auto-generate diagrams, or brainstorm interactively from scratch. Exports .drawio files with optional PNG/SVG/PDF export via draw.io desktop CLI.
aws-lambdaDesign, build, deploy, test, and debug serverless applications with AWS Lambda. Triggers on phrases like: Lambda function, event source, serverless application, API Gateway, EventBridge, Step Functions, serverless API, event-driven architecture, Lambda trigger. For deploying non-serverless apps to AWS, use deploy-on-aws plugin instead.
aws-lambda-durable-functions>
aws-lambda-managed-instances>
aws-lambda-microvms>
aws-serverless-deploymentAWS SAM and AWS CDK deployment for serverless applications. Triggers on phrases like: use SAM, SAM template, SAM init, SAM deploy, CDK serverless, CDK Lambda construct, NodejsFunction, PythonFunction, SAM and CDK together, serverless CI/CD pipeline. For general app deployment with service selection, use deploy-on-aws plugin instead.
aws-step-functionsBuild workflows with AWS Step Functions state machines using the JSONata query language. Covers Amazon States Language (ASL) structure, state types, variables, data transformation, error handling, AWS service integration, and migrating from the JSONPath to the JSONata query language.
aws-transformMigrate, modernize, and upgrade codebases to AWS. Run analysis on repos for tech debt, security vulnerabilities, and modernization opportunities. Transforms .NET Framework to .NET 8/10, mainframe COBOL to Java, VMware VMs to EC2, SQL Server to Aurora, and upgrades Java/Python/Node.js versions and AWS SDKs. Use when the user says "migrate .NET to AWS", "upgrade Java to 17/21", "modernize COBOL", "modernize mainframe", "move VMware to EC2", "convert SQL Server to Aurora", "upgrade Python version", "migrate AWS SDK", "transform this codebase", "analyze for issues", "find tech debt", "what tech debt", "security vulnerabilities", "CVEs", "what's wrong with my code", "assess my repos", "where do I start", "find what's outdated", "analyze my repos", "AWS Transform - continuous modernization", "continuous modernization" or "continuous-modernization". Don't use for infrastructure provisioning, CI/CD pipelines, or general coding tasks.