There are several ways to store the physical location of IoT devices. In the case of static gadgets (smart home appliances, for example), we can leverage the AWS IoT Thing Groups. Thing Group represents a logical subset of the fleet. We use Thing Groups in various scenarios, one of which is to describe the physical location of assets. We can send a no-one-home MQTT message to all devices in the hall group to switch them into the desired state.

Knowing infrastructure costs is critical to validate a business case, but there is no way to assign AWS infrastructure costs generated by connected Devices directly to IoT Things representing them. To solve that challenge: Create a Billing Group with desired Tags, Add IoT Things to that Billing Group. AWS generates a cost allocation report with usage and costs aggregated by Tags. Use Tags representing business units and applications to organize your expenses.

Can we use the same certificate for multiple connected devices? I received that question during my last presentation. The short answer is: yes, we can. The long answer is: no, we should not! I explained my reasoning in this video. Feel free to message me with any IoT-related questions! Can we use the same certificate for multiple connected devices? I received that question during my last presentation. The short answer is: yes, we can.

The AWS IoT Thing Type is described using Attributes and Tags. I created a short video describing this topic. Sometimes people confuse Attributes and Tags of the Thing Type, so I decided to write how I use them. I use Attributes to describe the characteristics of connected devices. I typically use values like: firmware version hardware version vendor I use Tags to describe the characteristics of AWS infrastructure. I typically use values like:

Today I’ll write about the parallel MQTT sessions between a single Device and AWS IoT Core. I will also share an unexpected finding! To be honest, I am not sure if that is a bug or a feature of the AWS IoT Core. Introduction The AWS IoT Core message broker does not allow two clients with identical client ID to stay connected at the same time. After the second client connects, the MQTT Broker (part of the AWS IoT Core) closes the existing connection.

There are several ways devices can ingest data into the AWS cloud backend. Knowing available options enables choosing the right approach for a specific objective. Some use cases require sending frequent telemetry messages to AWS and storing them in the S3 Bucket. Putting every message independently to S3 would be very expensive due to the number of S3 API calls. Other scenarios demand transferring images or huge binary files from devices to AWS.