Introduction During the Internet of Things engagements, we need to adapt our solution to the capabilities offered by existing hardware and/or firmware. In some cases, our devices might not be able to use “fancy” MQTT clients. Is there a way to connect those devices to the AWS IoT Core? One of the possible options is to use the HTTPS protocol to publish messages from those devices to AWS. Limitations of the HTTPS protocol Before I present how can we send messages to AWS IoT Core using the HTTPS protocol, I want to underline some important limitations of this approach:

Overview In this post, I will present differences in AWS IoT infrastructure management using CLI, CDK, and SDK. As an example, we will create an IoT Thing using all of those approaches. Setup CLI The AWS Command Line Interface (AWS CLI) enables interaction with AWS services using commands invoked in a shell. Creating an IoT Thing using the AWS CLI is simple: 1 2 3 4 5 6 7 aws iot create-thing --thing-name cli-thing-0001 # { # "thingName": "cli-thing-0001", # "thingArn": "arn:aws:iot:eu-west-1:693854281758:thing/cli-thing-0001", # "thingId": "0f17b3b9-c77c-442e-9a25-ff04108729ef" # } We can check the outcome by invoking the following command:

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.