lambda-labs-gpu-cloud

Provision and manage Lambda Labs GPU cloud instances for ML training and inference.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill lambda-labs-gpu-cloud-kaminocorp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lambda-labs-gpu-cloud
Source: https://github.com/kaminocorp/hermes-alpha-hunter/tree/main/skills/mlops/cloud/lambda-labs
Command: npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill lambda-labs-gpu-cloud-kaminocorp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lambda-cloud-client, and includes references (resource) components.

What problem does it solve? Running large-scale ML training and inference requires dedicated GPU infrastructure, but provisioning, configuring, and managing cloud GPU instances involves complex API calls, SSH setup, storage management, and distributed training configuration that slows down ML workflows. ## Core Features & Use Cases - GPU Instance Management: Launch, monitor, and terminate on-demand GPU instances (B200, H100, A100, A10, V100) via the Lambda Cloud Python API or curl-based CLI. - Persistent Storage & Filesystems: Attach NFS filesystems at launch to persist datasets, checkpoints, and models across instance restarts. - Distributed Training & 1-Click Clusters: Configure multi-GPU DDP/FSDP training and multi-node Slurm clusters with InfiniBand for 16-512 GPU workloads. - Use Case: Fine-tune a 70B LLM by launching an 8x H100 instance with an attached filesystem, running accelerate-based training with checkpoints saved to persistent storage, then terminating the instance when done. ## Quick Start Ask the agent to launch a Lambda Labs GPU instance with your SSH key and attached filesystem, then connect via SSH to start training.

Frequently Asked Questions about lambda-labs-gpu-cloud

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I launch a Lambda Labs GPU instance with Python?▼

Install lambda-cloud-client, configure it with your API key, and call launch_instance with a region, instance type name like gpu_1x_h100_sxm5, and your SSH key names. Instances typically become ready in 3-15 minutes depending on GPU count.

Which Lambda Labs GPU should I use for LLM fine-tuning?▼

For 7B models, a single A100 40GB works well; for 70B models, use an 8x H100 instance. A10 or A6000 instances suit inference and development, while B200 offers maximum performance for the largest training jobs.

Lambda Labs vs RunPod vs Vast.ai for GPU cloud?▼

Lambda Labs provides dedicated instances with pre-installed Lambda Stack, persistent filesystems, and 1-Click Slurm clusters. RunPod offers cheaper spot and serverless options, while Vast.ai is a marketplace with the lowest prices but less managed infrastructure.

Does Lambda Labs storage persist after instance termination?▼

Only data on attached Lambda filesystems under /lambda/nfs persists across restarts and terminations. The root volume and local SSD are ephemeral, so always save checkpoints and datasets to an attached filesystem.

Why is my Lambda Labs SSH connection refused?▼

Connection refused usually means the instance is still initializing; single-GPU instances take 3-5 minutes and multi-GPU instances 10-15 minutes. Also verify the instance status is active and that your SSH key was added before launch.

How do I run multi-node distributed training on Lambda Labs?▼

Use 1-Click Clusters, which provide 16-512 H100 or B200 GPUs with Slurm and InfiniBand preconfigured. Submit jobs with sbatch or srun, launching torchrun across nodes with a shared master address and port.