I played around with deploying Nerves "firmware" to the cloud a while back. My notes are here: https://github.com/fhunleth/vultr_example. I originally looked at deploying to AWS, and it seemed feasible but I got a little lost in Amazon terminology. Getting something to work on Vultr was easy so I went there instead.
Some takeaways from doing this were:
- It's definitely possible.
- Server hardware and networking are simpler than what we have to deal with in the embedded use cases, so there are opportunities to streamline the tooling and base libraries for ease-of-use.
- Bootstrapping servers to work with Nerves needs work. For Vultr, I have an iPXE script to load the first image, but it's really tedious to use. From there on, you can update it via
nerves_firmware_ssh which is easier.
- I don't know enough about server deployment and operations to know what should be in the base Nerves image and what all is expected in the tooling. For example, it's possible to put Postgres in the base image (per the reddit post), but I'm not sure that's desirable. It seems easier (to me) to have a dedicated server for the database rather than combining it.
Anyway, Nerves in the cloud hasn't been a focus for me, but if others want to pursue it, I certainly would help on low level details.