I am losing money! Customers are not using my IoT system as they are supposed to! LM: First of all - congratulations! Your system delivers value for users! Not every IoT deployment does. Owner: But customers are not using my IoT system as they are supposed to and I am losing money! LM: That is often the case when customers are interacting with the solution differently than estimated in the business case.

Increased usage of an IoT service would decrease your margin! In what scenario the above statement could be true? The only possible reason that comes to my mind is poor service design. Areas of the increased costs due to the poor service design include: extra staff required to manually onboard and manage IoT devices manually over-provisioned cloud infrastructure to meet increased demand extra developers hired for fixing backend bottlenecks (when increased infrastructure does not fix the poor design issues) the churn of customers due to poor service quality All of the above leads to increased expenses and decreased income.

IoT device generates a running cost for the service provider. That fact is often overlooked by companies during PoC verification. In the long run, a connected device might cost more to operate than the income it generates for its provider. At a minimum, every connected device requires: connectivity to send telemetry data to a backend system processing capabilities of a backed system to analyze the telemetry data storage capabilities of a backend system to store data personnel to support customers and maintain backend infrastructure Depending on the specific service/product, the above cost factors may differ.

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: