/lm.jpeg
I believe in quality.
I do not support "fake it before you make it".
I write about #IoT, #security, and #aws related topics.

How to connect a fridge to the internet

The question What is the best answer to the following question: How to connect a fridge to the internet? The (short) answer Why would you like to do that? What do you want to achieve? The (long) answer There are multiple ways to connect a device (i.e. a fridge) to the internet (or, to be more precise, to some backed system). Let’s not start by listing all the ways to achieve that specific task.

The other side of the Internet of Things.

I often speak about providing business value using IoT solutions. My code is running on the factory floor equipment, medical devices, and in other environments. But do I really understand the end users? When medical devices were saving the lives of my kids, I realized that a single firmware/software bug might impact that process. Not every connected device is life/mission-critical, but someone or something depends on it. How should your system behave when it can not gather the required data?

AWS IoT Greengrass - permissions overview

Overview AWS IoT Greengrass is an open source Internet of Things edge runtime and cloud service. It enables efficient management of a huge fleet of IoT devices (called Greengrass Core Devices) and remote deployment + execution of applications at the edge. To provide those capabilities, Greengrass needs to be authorized to access other AWS Services. In this post, I will present the minimal set of privileges required for the Greengrass Core Device to operate.

Fake it until you BREAK it

I know many people that promote the following approach: “Fake it until you make it!” I strongly disagree with that statement as it puts the customer and/or end consumer at a huge risk. When someone “fakes it” (pretends to have required skills, knowledge, experience, etc.) and hopes to learn everything during the development, the final product will “break” sooner or later. That is why I think it should be called:

Edge vs Cloud

I often read/hear discussions “Edge vs Cloud”. The “Edge vs Cloud” is not a real conversation in the IoT space. Arguments in favor of the Edge: IoT devices operate at the Edge. data is generated and gathered at the Edge. Edge deployment ensures minimum latency for real-time applications. All of the above statements are true. Devices live at the Edge, gather data using sensors, and impact the environment using actuators.

Device x509 certificate rotation

I co-authored a post published on the official AWS IoT blog. I described the automated approach to rotate x509 certificates used by IoT devices. The proposed solution leverages managed AWS services and MQTT communication. That is a quite advanced topic, feel free to reach out if you have any questions. Link: https://aws.amazon.com/blogs/iot/how-to-manage-iot-device-certificate-rotation-using-aws-iot/