Native Particle data transport and encryption
There is no additional cost when building your project firmware. The services are there an there are several posts to incorporate webhooks to attach to various cloud service.
Searching the form will pull up a great many posts and/or tutorials and there is a great deal of overlap between posts. There are plenty of solutions.
Roll your own data transport
There are at least three SSL/TLS libraries in various stages of porting to the Particle platform. These come at GREAT cost. There is very little room left for a custom application.
wolfssl: published as wolfssl currently at version 0.0.1.
axtls : unpublished, still a work in progress.
All these libraries may start small (60-70k). The compiler does a great job at reducing firmware size if functions are not being called or utilized. As you begin to tap into more of the SSL/TLS library for encryption/decryption, the firmware size will go up. Sometimes substantially until it will no longer fit within the 128k allowed.
There are several folks asking about AWS API gateway. There are several forum posts about firmware status to support AWS API. It turns out this is not so easy. I’d like to wrap this up to continue with projects below so I can get on with other things.
I’d like to be able to get something working with the API (https://things.ubidots.com) as to expand the Particle Ubidots 2.1.12 library to use all the available API calls. I am perfectly content at the moment pushing data back and forth via python on a BBB/RPi3.
It would also be nice to talk to the losant platform for MQTT/Node-Red work.