Closed pmenn36 closed 3 years ago
Interesting. Can you share full command and config you ran so I can reproduce this issue?
Feel free to post additional details here if you are still having this issue. Flintrock does flag bad AMIs with a clear error, but perhaps there is some other code path you were hitting where Flintrock doesn't do such a good job.
When specifying my Flintrock configuration, I accidentally used an invalid AMI, but instead of telling me the AMI was invalid, it told me that my key pair was invalid (the key pair was perfectly valid). I eventually figured out the root issue, but that error message sent me down a rabbit hole for a bit!
This was the output: