Overview AWS IoT Thing Type helps organize, categorize, and search for IoT Things managed by the AWS IoT Thing Registry. This article is a continuation of my previous post - AWS IoT Thing Attributes - introduction All Things associated with a specific Thing Type have common attributes (like: manufacturer, serial number, color). To manage Thing Types we will use the AWS SDK for Python (Boto3). 1 2 3 4 5 6 7 8 9 import boto3 import json # A session manages state about a particular configuration.

Introduction There is a saying among Linux administrators - with great power, comes great responsibility. The same is true if you decide to use low-level tools (like Boto3) to manage cloud resources. You are in full control of your AWS services, and your responsibility is to handle them properly. Race condition A race condition can be difficult to reproduce because the end result is nondeterministic and depends on the relative timing between interfering processes.

Overview The IoT Thing is a virtual representation of a physical device or logical entity (for instance: an application). Following Thing properties describe an IoT Thing: Thing Name Thing Type Thing Attributes Thing Groups Billing Group AWS IoT Thing properties Thing Attributes Thing Attributes are key-value pairs that record information about the Thing (for instance: the hardware version or vendor). We can create an IoT Thing and define Thing Attributes using the AWS SDK for Python (Boto3).

Overview Security of Internet of Things is stretched from on-premise devices all the way to cloud services. It is a difficult and complex topic. I gathered some crucial materials to help you navigate in this space. AWS documents Securing Internet of Things (IoT) with AWS On 20th of December 2021, AWS published an updated version of Securing IoT with AWS whitepaper. It is a complete overview of AWS security services designed to protect IoT deployments; a must-read for everyone interested in building IoT solutions on AWS.

Design during Development - is that always a bad approach? typically that is the case The best practice is to Design before starting the Development. This approach provides multiple benefits: it is easier to update the design (for example, a UML diagram) than modify the software/hardware prototype; good design helps to manage the complexity (for example, by creating abstraction layers) and hide the logic of internal modules; during the design stage, we can identify future issues (for example, inadequate data structures) and fix them without modifying the already developed solution.

System design from the end-user perspective is an extremely important yet easily forgotten approach. I will use myself as an example. When I was designing a frame for the ‘autonomous’ lego car, I focused on the practical aspects. This frame should be: stiff, versatile, provide a space to attach sensors. My son (7y) understood all of the above but wanted to make this frame also look cool. Entertaining end-user experience is extremely important.