My friend wants to start breeding hens. He asked me if I know a solution to remotely open and close a chicken coop door. I replied that is a pretty simple solution - a single GSM-connected device with a door actuator. I would love to explain how to build, program, and connect it to AWS, but I knew that he don’t really care about technical details. Then he replied: “I just need to remember to send an SMS to remotely open and close those doors every day.

Overview Today I will present a sample approach to reduce the telemetry ingest costs by 84%. We will achieve that by properly designing the AWS infrastructure. I will also help you understand the output of the AWS Pricing Calculator and AWS infrastructure cost factors. Sample scenario Sample scenario We have 100 devices constantly connected to the AWS IoT Core. A single device sends 10 KB of telemetry data every 5 seconds.

The Internet of Things is a Value-Added Service (VAS), not an independent service. Recently I heard people saying that IoT is not an industry. Some generic IoT Platforms were discontinued. In my opinion, IoT is not diminishing, it is evolving. And I am not talking about the technology itself, but about our attitude toward it. The Internet of Things is not the final product or service. No one needs a connected “box” in their home, we need “washing machines”.

At a minimum, IoT is a feedback loop for your product. That is the “quickest win” of the Internet of Things initiative I can think of. You can enable the feedback loop by attaching the telemetry communication capabilities to your existing product. This way you can take a small step towards making your product “smart”. To be honest, sending telemetry data does not make your product “smart” - it enables a better understanding of how users are interacting with your product and implementing improvements based on gathered data.

Which device is the best to learn about the Internet of Things? That is a question I am asked frequently. Let me explain my perspective before answering that question. In my opinion, the Internet of Things is not a “single device”. I think about the IoT as an ecosystem of various connected devices cooperating to achieve a business outcome. Those devices are connected to diverse private and public networks and use various communication protocols.

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)