I am a huge fan of using precise AWS IoT Policies. To make them flexible yet restrictive I heavily use the IoT Policy Variables. Unfortunately, putting all of those best practices in place lead to: ❌ Deployment failed: Error: Stack Deployments Failed: Error: The stack named GGMainInfra failed creation, it may need to be manually deleted from the AWS console: ROLLBACK_COMPLETE: Resource handler returned message: "Invalid request provided: Policy cannot be created - size exceeds hard limit (2048)

Why Passwords are not equivalent to X.509 Certificates for IoT Devices? A Password is just a string of characters. It does not provide any information about the user - the User <-> Password relation is stored in some external system, it is not “embedded” into the password itself. A Password does not have any information about the expiry date. Once again, the expiry date is stored in some external system, it is not “embedded” into the password itself.

AWS IoT Greengrass is an open source Internet of Things edge runtime that can be installed on a hardware device. Greengrass Components are applications running on a Greengrass device. There are many Components, some provided by AWS, others created by independent developers. If there are so many Greengrass Components, then which of them is the most important? In my opinion, the most important Greengrass Component for production deployment is the aws.

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).