Stuck at "Waiting for SSM"

[NitriKx]

Original poster: https://github.com/gunar

Thoughts?

[kenanchristian]

Hi @kenanchristian, @gunar, @ms5 - can you please continue this thread here:
cloudrig/CloudRIG#7

I am trying to reproduce the issue, but it works my side.
What region are you running using?
What is the state of the EC2 instance that CloudRIG starts in the EC2 console?

Replying to the original thread,

I'm on ap-southeast-1 region, and the EC2 instance that cloudrig created is already running

[4Ply]

Thanks @kenanchristian
I can confirm that I am experiencing the same issue when using ap-southeast-1.

Please note that this does appear to leave a misconfigured instance living in EC2, which CloudRIG is unable to stop as the "stop" scripts are not uploaded to the VM.

Please ensure that you terminate these instances manually via the EC2 console, as well as the spot request from the Spot Request console (this is very important)

I am investigating the issue, and I will report back on any progress.

[4Ply]

Hey, sorry for the late reply, I had a hectic weekend!

The SSM Agent on the machine is unable to start up, showing the following error in the logs:
ERROR error occurred when starting core manager: Failed to fetch region. Data from vault is empty. Get http://169.254.169.254/latest/dynamic/instance-identity/document

Based on this this thread, it appears that this has something to do with the version of EC2Launch that is installed on the AMI, which is a very old version (v 1.3.2000080). The version history can be seen here

I am not too sure how to go about fixing this, as will likely require updating the AMI, and I don't know who owns it? @NitriKx @williamparry do you have any idea?

[NitriKx]

In fact CloudRIG is using AMI created by Parsec itself (and not very maintained). We plan to create CloudRIG dedicated AMIs, that will include the latest version of graphic drivers and AWS tools.