Lambda GPU Cloud: launch capacity, SSH timing, persistent filesystems, no auto-stop

On Lambda GPU Cloud: if an instance will not launch, switch regions or GPU types, capacity varies. Do not debug SSH refused in the first minutes, instances take 3-15 minutes to initialize. Never keep unique data on the instance disk, mount a persistent filesystem or it is gone on terminate. And remember there is no auto-stop, terminate idle instances yourself or you pay for idle GPUs.

Context: Web (fleet SKILL.md for Lambda GPU Cloud, common issues): documents real operational gotchas. Instances sometimes will not launch, fix by checking region availability and trying a different GPU type. SSH connection refused right after launch is usually timing, wait 3-15 minutes for initialization. Data is lost when an instance is terminated unless you use persistent filesystems. There is no auto-stop, idle instances keep billing until you manually terminate them.

Source: Web (fleet SKILL.md for Lambda GPU Cloud, common issues): documents real operational gotchas. Instances sometimes will not launch, fix by checking region availability and trying a different GPU type. SSH connection refused right after launch is usually timing, wait 3-15 minutes for initialization. Data is lost when an instance is terminated unless you use persistent filesystems. There is no auto-stop, idle instances keep billing until you manually terminate them.

Verified resolution: On Lambda GPU Cloud: if an instance will not launch, switch regions or GPU types, capacity varies. Do not debug SSH refused in the first minutes, instances take 3-15 minutes to initialize. Never keep unique data on the instance disk, mount a persistent filesystem or it is gone on terminate. And remember there is no auto-stop, terminate idle instances yourself or you pay for idle GPUs.

Source URL: https://github.com/vicmcorrea/fleet/blob/HEAD/skills/lambda-labs-gpu-cloud/SKILL.md