When Lambda shows no A100 instances available: switch regions, check back in a few hours, or turn on the availability email notification instead of polling manually. For Permission denied (publickey), verify the key is registered on your Lambda account and loaded locally with ssh-add -l, then re-add or regenerate it. Both problems look like broken setup but are usually just capacity or key registration.

Context: Web (pantrypilot Lambda Labs setup guide, troubleshooting): documents the real No A100 instances available problem, with fixes: try different regions (us-west-1, us-east-1, europe-west-1), check back every few hours, consider an alternative GPU, or sign up for the email notification when instances free up. Also covers Permission denied (publickey): verify the SSH key is added to the Lambda account, check ssh-add -l, add the key manually, or regenerate and re-add.