147. Spec coding with Kiro

What if AWS built an IDE to rival your favorite editor? Turns out they did!In this episode of AWS Bites, we dive into Kiro, an AI centric fork of VS Code that tries to turn an empty repo and a loose idea into working software. Kiro imports your VS Code world, then guides you through requirements, design, and a clear task plan before an agent gets to work. We share what clicked, what tripped us up, and how Kiro’s spec driven approach compares to Cursor or Claude Code. We also cover status, limits, pricing, and what this could become if AWS leans in with deep cloud integration. Stick around for our take on whether you should switch or wait.

Big shoutout to fourTheorem for powering yet another episode of AWS Bites. At fourTheorem, we believe the cloud should be simple, scalable, and cost-effective, and we help teams do just that. Whether you’re diving into containers, stepping into event-driven architecture, or scaling a global SaaS platform on AWS, or trying to keep cloud spend under control our team has your back. Visit ⁠⁠⁠https://fourTheorem.com⁠⁠⁠ to see how we can help you build faster, better, and with more confidence using AWS cloud!

In this episode, we mentioned the following resources:

• Kiro website: https://kiro.dev/
• Kiro docs on Agent Hooks: https://kiro.dev/docs/hooks/
• Kiro docs on Steering: https://kiro.dev/docs/steering/
• Kiro pricing plans blog: https://kiro.dev/blog/pricing-plans-are-live/
• Cargo Lambda: https://www.cargo-lambda.info/
• Episode 64: how do you write Lambda functions in Rust?: https://awsbites.com/64-how-do-you-write-lambda-functions-in-rust/
• Kiro GitHub issue: https://github.com/kirodotdev/Kiro/issues/2004
• Amazon Q developer CLI: https://github.com/aws/amazon-q-developer-cli

Do you have any AWS questions you would like us to address?

Leave a comment here or connect with us on X/Twitter, BlueSky or LinkedIn:

- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/eoins⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠https://bsky.app/profile/eoin.sh⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/eoins/

⁠⁠⁠⁠⁠⁠⁠- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/loige⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠https://bsky.app/profile/loige.co⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/lucianomammino/