Running Thinger.io IoT server on Amazon Web Services

Running Thinger.io IoT server on Amazon Web Services

Some weeks ago, we released Ubuntu Snap packages for installing the IoT server easily on Ubuntu Core, or Ubuntu 16.04. Today we have updated the instructions for a more reliable setup, specially for keeping the MongoDB instance running after reboot. Moreover, we have prepared an AMI (Amazon Machine Image) that allows deploying a sandboxed IoT server instance in a few clicks. As any other AMI, you can specify the instance size, network, security groups, SSH keys, and so on.

The only requirement is just to search the Thinger.io AMI image when launching the instance. Therefore, search for thinger in the Community AMIs. It is recommend to install the latest version available as you will get the latest features by default. Once installed, the server instance can be updated by using the snap mechanism.

For the security groups, it is recommended to open the SSH port, HTTP, HTTPS, TCP 25200, AND TCP 25202. Then you can use your own Internet of Things server by accessing your host IP address.

Enjoy! 🙂

Share this post

Comments (4)

  • Lo Reply

    Hello,
    I tried it, modified thingerclient.h to point toward the server IP, recompiled, disabled TLS in sketch, it tries to connect unsecure but always fails:

    [_SOCKET] Connecting to xx.xxx.xx.xxx:25200..
    [_SOCKET] Using secure TLS/SSL connection: no
    [_SOCKET] Error while connecting!

    But the instance is working fine, i can login, add device, logout etc.
    Where could be the problem? of course i opened all the ports advised and assigned the security group to the instance.
    Thanks

    August 25, 2017 at 10:45 pm
    • Alvaro Luis Bustamante Reply

      Hi, try to open a connection with a netcat or similar, to ensure you can connect to the server at port 25200. You can also try it from the server itself. The server will not reply, but if you type anything it will disconnect you quickly.

      August 25, 2017 at 10:55 pm
  • Lo Reply

    i used OSX network tool “port scan” and checked this port:
    Port Scan a démarré…
    Port Scanning host: xx.xxx.xx.xxx
    Open TCP Port: 25200
    Port Scan a terminé…
    So it tell it is well open

    August 25, 2017 at 11:51 pm
  • Lo Reply

    restarting the instance fixed the problem, it works now

    August 26, 2017 at 12:06 am

Leave a Reply

Your email address will not be published. Required fields are marked *