lambda-labs-gpu-cloud

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

14|5|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill lambda-labs-gpu-cloud-mlt-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lambda-labs-gpu-cloud
Source: https://github.com/MLT-OSS/hermes-agent-go/tree/main/optional-skills/mlops/lambda-labs
Command: npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill lambda-labs-gpu-cloud-mlt-oss

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 the console, Python API, or curl-based CLI. - Distributed Training Setup: Configure multi-GPU and multi-node training with PyTorch DDP, FSDP, DeepSpeed, and Slurm-based 1-Click Clusters with InfiniBand. - Persistent Storage & Cost Control: Attach persistent filesystems for checkpoints and datasets, and apply cost-optimization strategies like right-sizing GPUs and checkpointing. - Use Case: You need to fine-tune a 7B LLM. Launch an 8x A100 instance with an attached filesystem, SSH in, run distributed training with torchrun, and save checkpoints that survive instance termination. ## Quick Start Ask the agent to launch a single H100 GPU instance on Lambda Labs in the us-west-1 region using your configured API key and SSH key.

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 via 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 use for LLM fine-tuning?

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

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

Lambda Labs provides dedicated instances with pre-installed Lambda Stack, persistent filesystems, and no egress fees. RunPod offers cheaper spot and serverless options, while Vast.ai is a marketplace with the lowest prices but less consistency.

Does Lambda Labs support multi-node distributed training?

Yes, Lambda Labs supports multi-node training via 1-Click Clusters with 16-512 H100 or B200 GPUs, Slurm scheduling, and 400 Gb/s InfiniBand. You can also manually run torchrun across multiple instances in the same region.

Why is my Lambda Labs instance data lost after termination?

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

Why can't I SSH into my Lambda Labs instance?

SSH connection refused usually means the instance is still booting, which takes 3-5 minutes for single-GPU and 10-15 minutes for multi-GPU instances. Also verify your SSH key was added to Lambda before launch and that port 22 is open in the firewall.