Thank you for your post.
In the FileMaker Cloud console, check the Notifications in the upper right. Are there any reports listed? If so, then turn on email notifications. See Knowledge Base Article #16178 for more information:
You can also reboot the instance from the FileMaker Cloud console by going to Configuration tab, clicking on System Configuration, and clicking Refresh to the right of the instance.
So my question is this, if the filemaker server process crashes, how do I setup an alert to reboot the instance? Or at least send me an email. I expected something like this to be built into it automatically.
It is actually built in (except for the email). Unlike the on-premise regular FMS, the Cloud one has a 'robot administrator' that monitors FMS and brings it back to life where necessary.
Sounds like your problem was not with that and that it was running all the time, just that you could not get to it?
You can download the event log from the admin console, you may want to do that and see if it shows any relevant entries.
I ended up destroying the instance and starting over. Moving the data from the old volume to the new one.
The problem was the fmhelper file wouldn't connect to the server that it wanted to "phone" home as it may be.
My point was that the servers should be setup to detect if fmserver is running and restart the process independent of being able to ping back to some central server of filemaker-cloud. Also that if they are going to require to use the amazon ec2 provided dns servers instead of your own - that should be documented.