Why Kiro Just Killed Manual AWS Diagrams

Hey 👋🏽

​

Big news: We launched our YouTube channel! 🎬

We've published 7 videos so far and are almost at 800 subscribers. Our goal is to keep a weekly rhythm, so expect fresh content every week. If you haven't subscribed yet, here's the link.

​

No exciting AWS news this week. If you've spotted something interesting, let us know!

​

In this issue, we talk about creating AWS architecture diagrams. As engineers and architects, one of our main tasks is creating architecture diagrams. I've tried every possible way to create them:

• Lucidchart
• draw.io
• Miro
• Excalidraw
• Diagrams as Code
• …you name it.

​

Hours spent dragging boxes around, hunting for the right icons, trying to make everything line up. AI with Kiro gives us a promising alternative. You describe your architecture in plain English, and it generates the diagram for you.

​

​

​

​

📚 This Week's Deep Dive Let's face it: drawing AWS architecture diagrams is no fun. You spend hours dragging boxes around, trying to make everything line up. Your diagram ends up looking like a kindergarten art project compared to the polished ones in AWS whitepapers. Kiro with MCP servers tries to change this. You describe your architecture in plain English, and it generates the diagram for you. No more hunting for icons or fighting with alignment. What you'll learn: How to set up Kiro with diagram MCP servers Best practices for prompting (being specific matters!) Real examples from simple APIs to multi-tier architectures Where this approach falls short (it's not perfect) The results aren't 100% deterministic, and text placement can be messy. But for quick documentation or getting a visual starting point, it's a useful addition to your toolkit. 🚀 Read the Full Tutorial →

​

Summary

That's it for this week! Don't forget to subscribe to our YouTube channel if you haven't already. We're publishing weekly and would love to see you there. See you soon! Sandro & Tobi