Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Spot requests fail when no SSH key is configured #16
While playing around with autospotting, I configured a Launch Configuration that did not define an SSH key. In this setup, the spot requests failed with this error message:
It would be nice if autospotting supported this setup.
AutoSpotting couldn't care less about this, but unfortunately it seems the AWS spot request needs that field, even if AutoScaling doesn't need it.
It's likely one of those cases that show how AWS EC2 was built by different teams that didn't really care about synchronizing their JSON fields.
You can try launching a spot request with the AWS CLI tool that is also missing the SSH key field, if that works, then it is indeed an autospotting bug and I'll have to look into it in more detail.
I tried it out using the AWS CLI. When the field was empty, I got exactly the error message that autospotting produced. But when I completely removed the KeyName field from the JSON, the request works and I get an instance. Autospotting would have to do the same.