It all started typically - that person contacted me on LinkedIn asking for assistance in designing and building an IoT-powered product. We met, discussed the business idea, found a common ground, and agreed to start in a month. Time has passed, and I haven’t heard from that person. Ok, I thought, yet another lead that went south. I decided to give it one last try and sent an email asking for confirmation that the initial agreement was no longer valid.

I’ve got access to numerous AWS accounts and typically use my phone as the MFA (Multi-Factor Authentication) device. That is a handy, secure, and cost-effective solution. There is a specific case in which I do recommend using a hardware security token as the secondary MFA. I use it to protect access to the Root User of the AWS Management Account. Let’s break this down: ✅ The Root User has unlimited permissions, can create and destroy any AWS infrastructure, and manage other users in that account.

Unlock IoT Flexibility: The Decoupled Power of MQTT MQTT enables the decoupling Publishers from Subscribers. This might sound technical, but it has implications for flexibility and scalability in IoT solutions. Let’s explore why this feature is one of MQTT’s greatest strengths. Your browser does not support the video tag. The Magic of Decoupling: Publishers & Subscribers in MQTT At its core, MQTT (Message Queuing Telemetry Transport) is a lightweight messaging protocol ideal for constrained devices and low-bandwidth, high-latency, or unreliable networks – common scenarios in IoT.

Introduction Amazon Q Developer is a generative artificial intelligence (AI) powered conversational assistant that can help you understand, build, extend, and operate AWS applications. You can ask questions about AWS architecture, your AWS resources, best practices, documentation, support, and more. Context - how to customize solutions AI generates Amazon Q context enables fine-tuning Amazon Q to generate solutions according to your specific needs. This is how I use it. Overall Context Structure For the greatest flexibility, I manage contexts on three distinct levels:

People say that every challenge we encounter is an opportunity in disguise. That is probably true, but that does not mean it is a good spot to be in. When I decided to offer advisory services on my website, I wanted to implement the payment system in the “standard way.” I resisted the temptation to implement everything myself and researched platforms offering product catalogs and payment integration. I found a solution, integrated it with Stripe and my website, and happily used it for over a year… until this morning.

Introduction Developing an Internet of Things (IoT) solution involves addressing the complexities of backend infrastructure, particularly when the system must accommodate multiple clients or tenants. A fundamental architectural decision concerns whether to prioritize repeatability or scalability in the backend design. This choice carries significant consequences for the efficiency of customer onboarding processes, cloud costs, and the operational overhead associated with system maintenance. In this analysis, I will outline these two architectural paradigms, providing considerations for multi-tenant environments.