Qiita - 人気の記事AWSのAIエージェント、Kiro CLIで開発を加速させよう
https://qiita.com/miruky/items/145fa2461daf6ded64e1?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
ryohi5557
Sébastien StormacqThere is a full RAG engine in Kiro-CLI. No vector database installation, no chunking, no dealing with Bedrock models.
It helped me to write the recent S3 anniversary blog post.
Here is how 👇
https://stormacq.com/2026/03/14/how-kiros-knowledge-base-helped-me-write-the-s3-anniversary-blog-post/
How Kiro's Knowledge Base Helped Me Write the S3 Anniversary Blog Post
Today, twenty years ago, AWS quietly launched Amazon S3. What started as a simple object store with two primitives, PUT and GET, became the foundation upon which large enterprises built their data lakes, and with the introduction of S3 Vectors, is now powering a growing number of AI workloads. I had the honour of writing the S3 anniversary blog post for AWS. For that post, I wanted to go beyond the usual narrative and share concrete technical details about the infrastructure behind S3 when it first launched. I interviewed Senior Principal Engineers who were around twenty years ago and collected stories about the early days. But stories alone weren’t enough. I needed data. What was the initial storage capacity? How many objects could the system hold? How much bandwidth was available? To publish numbers like these in an official AWS blog post, anecdotes don’t cut it. I needed evidence.
Snapp iOS WeeklyLike it or not, AI-powered coding is here. This article shares a spec-first approach to Swift development using AWS's Kiro - but the patterns transfer easily to other coding agents. Definitely worth reading.
🔗: https://stormacq.com/2026/03/04/building-wispr-with-kiro-a-spec-first-approach-to-swift-development/ by Sébastien Stormacq (@sebsto)
How I built a production-ready macOS voice dictation app in 1.5 days using AI-assisted development, without writing a single line of code myself.
https://stormacq.com/2026/03/04/building-wispr-with-kiro-a-spec-first-approach-to-swift-development/
Alejandro BaezForget #kiro is locked down as hard as fort knox.
Read through their specs documentation. It's an absolutely stellar pattern to follow. Write your requirements and track design of your requirements.
immensely valuable advice on how to build software in general. 😅
JM FloresFirst impressions on #Kiro (as a front-end developer):
- It does a decent job at refactoring code, tracing component dependencies, writing docs, and creating test data.
- Translating Figma designs into React components is hit-or-miss - more miss than hit in my experience. Perhaps there are certain ways of composing mockups that would yield better results.
- Spec-driven development (a fancier form of vibe coding, I guess?) looks quite promising, but I'll have to play with it some more.
Simon D.Pannes chez AWS dues à son agent IA : Amazon se défausse sur ses employés
https://next.ink/225523/pannes-chez-aws-dues-a-son-agent-ia-amazon-se-defausse-sur-ses-employes/
Plusieurs pannes chez AWS sont liées à l’utilisation en interne de ses propres agents IA par ses ingénieurs. L’entreprise qui a lancé son agent Kiro en assurant qu’il allait « au-delà du vibe coding » rejette la faute sur ses employés qui auraient laissé faire son IA.
***
Encore mieux que les stagiaires de #BFMTV
#AWS #AI #IA #Kiro #Amazon #GAFAM
FreezenetAmazon Employees Blames AI for AWS Outage in December
Amazon employees have blamed the AI, Kiro, for deleting and attempting to recreate the environment. Amazon denies this.
https://www.freezenet.ca/amazon-employees-blames-ai-for-aws-outage-in-december/
#News #Technology #AI #Amazon #AWS #Claude #fail #Kiro #outage
Pivot to AIAmazon Web Services vibe-codes itself an outage or two
