Overview AWS IoT Greengrass is an open source Internet of Things edge runtime and cloud service. It enables efficient management of a huge fleet of IoT devices (called Greengrass Core Devices) and remote deployment + execution of applications at the edge. In this post, I will present a way to deploy the infrastructure required by Greengrass. Note: This setup is for educational purposes. It can be used for production deployment but is not designed for onboarding a huge fleet of Greengrass devices.

How relevant is talent in IT? very relevant somehow relevant not relevant Note: This is my personal opinion based on my personal experience. I am not very talented. As a kid, I had a hard time learning to read and write. When I tried to learn my first programming language, I was not able to understand the concept of variables. Over the years, I spent many hours learning some advanced programming ideas.

Intro While working on the AWS IoT Greengrass training, I had the following thought: Which IoT resources should be managed by CDK? For educational purposes, I wanted to declare every single component required by Greengrass using CDK. I was aware that was not the best practice approach, but I wanted to present important concepts regarding Greengrass. In my previous post, I demonstrated how to create a Thing Group (natively not supported by CDK or CloudFormation).

How to create an IoT Thing Group using CDK? By default, we can not manage IoT Thing Groups using AWS Cloud Development Kit (CDK). CDK deploys infrastructure using CloudFormation and CloudFormation does not support Thing Groups. Today I want to share an elegant solution for this challenge. CDK Constructor I propose to create a custom CDK Constructor. Constructor represents a specific resource and enables the management of the corresponding AWS infrastructure.

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.