MQTT and new AWS IoT service

Any news, good or bad, on getting support for either MQTT-TLS or HTTPS in the Photon?
Thanks :smile:


Any one get this working with AWS IOT?

Hello Sharding,
i want to update a device shadow through lambda function,and am new to lambda functions and not very well used to lambda nodejs coding,so can u pls help me on how to update a device shadowing by using lambda functions.
Hope you do the needfull.

Any one get this working with AWS IOT?

Presumably it won’t happen until there is legit TLS support on Particle. Here’s an effort/discussion: Any mbed TLS efforts yet?

The “what about us???” attitude from Particle seems to miss the point, many of us have large stacks on AWS already, which makes service integration much faster (especially given limited http/https support, which means REST can’t be used with existing solutions).

I use the programmer shield to do re-flash the photon to
have a direct connection to AWS IOT. By doing that you will loose all
the feature of the original firmware.

I successfully connect to AWS IOT from Photon.

I found this article on Broadcom’s forum. (I post my modification on this forum too)

Download and unzip the (need to register)

By following the article you will create a new profile.
If you follow the step by step at the end of the post you will modify an existing profile.
This will allow you to run Broadcom’s example where you can connect to AWS IOT through MQTT.


+1 for AWS IoT SDK support. I know it’s not easy but would be great to have it officially supported in particle (or at least a MQTT/TLS with client side certificates for device authentication).

+1 for AWS IoT support

The Adafruit WICED WiFi Feather now supports AWS IoT:

The Adafruit WICED WiFi Feather now supports AWS IoT

Whoa, that’s huge.

…anyone want to buy my assorted Particles?

@gusgonnet @sharding Hey guys, how close is what you were doing with Amazon AWS to this implementation I just ran across?

I don’t have time to read the article right now, but that very high-level diagram exactly matches what I’m doing.

1 Like

My project is pretty similar on the “front-end” (up until the api GW): :slight_smile:


1 Like

I still have a lot to learn but do you think using DynamoDB and this Amazon AWS structure is one of the lowest cost ways to database sensor data sent from a remote Photon or Electron?

I have a product, and I want to database data it generates every min or so.

I’ve tried using Node-Red to receive data sent from a Photon and then send that data to a Mongo DB database but I’m new to this, and I’m not sure what all my options are.

I do hear Amazon AWS is a big player in the market, and I would assume their pricing is as good as any out there due to their scale of business.

The nice thing about the AWS solution from a cost standpoint is that for the most part those services are all pay as you go. So it starts out almost free, and grows only as your needs grow. As your project gets larger, you do need to proactively manage the costs because it can get expensive when you’re not paying attention, and a lot of waste can work its way in over time (e.g. unneeded tables or instances hanging around). But I think it’s a pretty good starting point.


Yes, that does sound good. I’m just looking for the most efficient and cost-effective solution possible.

So can you tell me what the big difference is between the using the Photon & Webhooks or MQTT to send the data to AWS vs. what Adafruit has going on that allows you to connect directly to AWS using the method as mentioned above and linked below? :

The Adafruit WICED WiFi Feather now supports AWS IoT:

Hey, one thing different is the device shadow feature, that allows you to see (or I believe change as well) a device state or variables even it is not connected to the internet:

This shadow feature you get when using MQTT or HTTP. I think you can’t get it with webhooks (or at least I don’t know how to).

An alternative to your project could be to use other, more simplified services, like,,
Why? because those services already abstracted many things that you will have to deal with yourself if using AWS.
This is how I see it:
AWS: is like programming in assembler or C => you get full control and full headaches, since you have to manage everything yourself.
ubidots or similar: is like programming in python or java => you get some sort of control, but the higher level of the language helps you develop faster and it already made things available for you in an easier way.
I’ll tell you this story to support my view: I spend around a week to make my first use case work in AWS (due to all things involved), and only couple of hours to make my first dashboard in ubidots.


I’m doing something very similar as well:

WebHook -> API Gateway -> Lambda -> DynamoDB

I wish Particle supported SSL so MQTT could work – seems like it would be a lot easier.


Hi Ryan ,
in case using a Google spreadsheet as a DB is an option in your scenario, you can take a look at the following article:

Thanks @gusgonnet for remembering me on this.

After reading up some more on the DynamoDB + Lambada functions it’s looking like its the best path for what I’m trying to do with a connected product at scale.

For the one-off projects, Ubidots has always worked perfectly for me but can get expensive when scaled up.

yes it could…

@nicj @gusgonnet @sharding

So what would be the benefit if the Particle devices supported SSL so MQTT could work?

How would the data flow to Dynamo DB change if SSL was supported on the Photon like it is on the Adafruit version?

I’m just trying to understand the differences between the 2 different methods of getting data into the DynamoDB database.

If SSL was supported on the Photon could the Lambada function and fees be skipped?