How to use the AWS IoT Core Policy Variables to create fine-tuned access permissions for connected IoT Devices? IoT Policy To put it simply, IoT Policy allows IoT Device (represented by the IoT Thing) to send and receive MQTT Messages on specified MQTT Topics. NOTE: The IoT Policy is attached to the X.509 Certificate, not to the IoT Thing. I explained the IoT Thing in my previous post. Sample IoT Policy Let’s start with a simple IoT Policy:

Did you know that you can register the X.509 Certificate in the AWS IoT Core using AWS Cloud Development Kit (CDK)? Simplified registration process: generate the Private Key locally based on that Private Key generate the Certificate Signing Request (CSR) use the below code to register your X.509 Certificate based on generated CSR 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 from aws_cdk import ( Stack, aws_iot as iot, CfnOutput ) from constructs import Construct class IotCdkStack(Stack): def __init__(self, scope: Construct, construct_id: str, **kwargs) -> None: super().

Overview Fleet management is a very important concept in the Internet of Things domain. Today I want to evaluate strategic options regarding the initial setup of the IoT fleet. There are a few technical approaches to this topic. As always, I recommend starting with the business considerations. Business considerations Question: How do you define the IoT fleet? LM: IoT fleet consists of many IoT devices connected to some kind of backend (i.

“It depends” should not be the answer “It depends” is a typical answer of an (experienced) consultant. I hear this saying quite often. For a long time, I thought the same way - there are always multiple ways to achieve the required functionality. Some time ago I changed my mind. Let me take you on a tour of my personal development as a consultant. Chapters in a consultant’s career Below I described chapters in a consultant’s career based on my own experienced.

The biggest compliment I received regarding my solution design diagrams was something along those lines: “I do not understand the technical aspects represented on your diagram, but the overall idea looks very clear to me." Sometimes I see technical diagrams by very smart/experienced professionals that are extremely hard to follow. I know that those people know and understand what they are talking about, but those designs are not representing that.

I had an opportunity to speak at the AWS Pop-up Hub. I lead an expert-level, deep dive session about the AWS IoT Greengrass service. During my presentation, I used only one IoT Device, but I explained how to effectively onboard and manage a huge number of connected Greengrass devices. I covered the following topics: How to use the Greengrass Fleet Provisioning plugin to generate unique credentials for every connected device. How to create a custom configuration file to fine-tune the Greengrass service.