Error during/after 'bootstrapping' when starting a new syme session

[jprof]

When trying to launch a new session for collaboration syme reports an error. The provided ssh command does not work, although the EC2 instance is started when investigating my AWS console. Trying to halt from the syme UI does not work. This was also reproduced by @hlatki. This was all seen via the heroku app running at: https://syme.herokuapp.com/

[leathekd]

The error on startup and the broken halt button are working now but the ssh command is still broken. That said, the instance is started and provisioned so you can grab the IP address or hostname from the AWS console and ssh syme@<AWS IP ADDR> and it should work.

[leathekd]

Oops, sorry, it still reports "error" at startup, but it actually works. I believe the error at startup is related to #44