Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Launching Windows AMI sometimes timeout on EC2. What is going on?

April 26, 2017AMI EC2 going launching timeout Windows

0

Posted

Launching Windows AMI sometimes timeout on EC2. What is going on?

1 Answer

0

Posted

Kaavo Workflow engine waits for the Windows SSH service to come up before start executing the configuration/deployment workflows. After the Windows server is up on EC2, Amazon EC2 reboots the server and run some AWS scripts before making the fully functional server available. Sometimes it is possible that after the SSH service on Windows comes up before the Amazon does the soft reboot, IMOD engine start configuring the server and the reboot during configuration of the server by Amazon EC2 causes problems and server configuration timeout. We have addressed this issue by installing a boot script on Windows to make sure that SSH service is started only after the server is ready after Amazon finishes the soft reboot. The Windows JIRA example in IMOD has the Kaavo AMI with the proper work around the Amazon soft boot. If you want to use your own Windows AMI instead of Kaavo provided image from IMOD please read these instructions. Note: IMOD engine uses SSH to automate the deployment and run-