AWS IoT VS Zephyr RTOS

In this blog post series, we will look at a simple example of modeling an IoT device process as a workflow, using primarily AWS IoT and AWS Step Functions. Our example is a system where, when a device comes online, you need to get external settings based on the profile of the user the device belongs to and push that configuration to the device. The system that holds the external settings is often a third party... - Source: dev.to / about 1 year ago

Iot - MQTT broker to send messages to the Raspberry Pi. - Source: dev.to / over 2 years ago

" Amazon Web Services offers a broad set of global cloud-based products including compute, storage, databases, analytics, networking, mobile, developer tools, management tools, IoT, security and enterprise applications. These services help organizations move faster, lower IT costs, and scale. AWS is trusted by the largest enterprises and the hottest start-ups to power a wide variety of workloads including: web and... Source: over 2 years ago

AWS IoT Core - message broker between all devices and AWS. - Source: dev.to / over 2 years ago

If you have to ask, then you should be using AWS by default. They have plenty of IoT services for you to fiddle around with and get started. Source: over 2 years ago

I can recommend [Zephyr](https://github.com/zephyrproject-rtos/zephyr) for these things. Source: over 2 years ago

Zephyr, RIOT, NuttX are all open source RTOSes happy about contributions. Source: over 2 years ago

Microcontrollers are a good start. Boards are cheap and sensors are plentiful. You could get a yet unsupported board and port RIOT, Zephyr or NuttX. Source: over 2 years ago

Zephyr Project: Update to 2.5 or later.  Patches are available for prior supported versions. See the Zephyr security advisory for more information. Source: over 2 years ago