Urgent.News

What's breaking now, across thousands of outlets.

Tech

Your Terraform IAM Policies Are Haunted (Here's How I Exorcised Them with Kiro)

Note: This post is written as part of my submission for the **Kiroween 2026 * hackathon.* Most AWS accounts have a zombie problem. Not the movie kind. The s3:* , dynamodb:* , and iam:PassRole on Resource = "*" kind. Policies written in a rush during a Friday deployment. Never touched again. Silently waiting for one leaked key to turn a minor bug into a full-blown breach. Everyone knows you should…

This article, written for the Kiroween 2026 hackathon, explores the pitfalls of using AI for managing AWS IAM policies and introduces Dr. Kiro, an autonomous IAM least-privilege engine. The author shares how they developed FrankenGuard, an AI DevSecOps tool that enforces strict guardrails to prevent AI from accidentally deleting crucial permissions during deployments.

The first step of Dr. Kiro's remediation process involves cross-referencing Terraform IAM policies with real AWS CloudTrail logs. This helps identify unnecessary wildcards and other risky configurations. Next, the tool uses a native C++ Tree-sitter HCL2 engine to precisely edit the relevant AST nodes, preserving surrounding resources and formatting.

This ensures the resulting Terraform code remains clean and functional. Finally, Dr. Kiro provides a visual dashboard to monitor the impact of these changes, effectively reducing vulnerability risks by over 90%.

Key takeaways from the article include the importance of separating AI reasoning from code mutation, implementing robust guardrails, and using deterministic AST tools like Tree-sitter for secure code editing.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

More from Thursday 19 November →