lambda-labs-gpu-cloud

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

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/xu1713/openhorse --skill lambda-labs-gpu-cloud-xu1713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lambda-labs-gpu-cloud
Source: https://github.com/xu1713/openhorse/tree/main/openhorse/openhorse/optional-skills/mlops/lambda-labs
Command: npx skills add https://github.com/xu1713/openhorse --skill lambda-labs-gpu-cloud-xu1713

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Provisioning dedicated GPU infrastructure for ML training and inference is complex and expensive. This Skill guides you through launching, configuring, and managing Lambda Labs GPU instances and clusters so you can run training jobs without managing hardware. ## Core Features & Use Cases - Instance Lifecycle Management: Launch, monitor, and terminate GPU instances (B200, H100, A100, A10, and more) via console, Python API, or curl CLI. - Persistent Storage & Training Workflows: Attach persistent filesystems, checkpoint models, and run single-GPU, multi-GPU (DDP/FSDP), or multi-node Slurm cluster training. - Use Case: You need to fine-tune a 70B LLM. Launch an 8x H100 instance with a persistent filesystem, SSH in, run distributed training with torchrun, and save checkpoints that survive instance termination. ## Quick Start Ask the assistant to launch a Lambda Labs GPU instance with your SSH key and walk you through connecting and starting a training job.

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 GPU instance on Lambda Labs?

Launch a Lambda Labs GPU instance through the cloud console, the Python lambda-cloud-client API, or curl against the REST API. You must add an SSH key before launching, select a GPU type and region, and optionally attach a persistent filesystem.

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

For fine-tuning a 7B model, a single A100 40GB works well; for 70B models, use an 8x H100 instance. For inference, A10 or A6000 instances are cost-effective, while B200 instances suit maximum-performance training.

Lambda Labs vs RunPod vs Vast.ai for GPU training?

Lambda Labs offers dedicated instances with pre-installed Lambda Stack, persistent filesystems, and no egress fees. RunPod is better for cheaper spot instances and serverless endpoints, while Vast.ai is a marketplace with the lowest prices.

Does Lambda Labs support multi-node distributed training?

Yes, Lambda Labs 1-Click Clusters provide 16-512 H100 or B200 GPUs with Slurm, InfiniBand networking, and pre-installed NCCL and PyTorch. You can also run multi-node torchrun jobs across regular instances in the same region.

Why is my data lost after terminating a Lambda Labs instance?

The root volume on Lambda Labs instances is ephemeral, so all local data is deleted on termination. Attach a persistent filesystem at launch time and store datasets, checkpoints, and outputs under /lambda/nfs/<filesystem_name>.

Why is my Lambda Labs SSH connection refused?

SSH connection refused usually means the instance is still initializing, which takes 3-5 minutes for single-GPU and 10-15 minutes for multi-GPU instances. Verify the instance status is active and confirm you are using the correct IP and SSH key.