Tags: Kiro

Amazon Web Services experienced a 13‑hour outage in December after its AI coding assistant, Kiro, deleted and recreated an environment it was working on. The incident, which affected parts of mainland China, was traced to a human error that gave the bot broader permissions than intended. Amazon says the outage was limited and emphasizes that the root cause was the human‑driven permission issue, not the AI itself, and notes that safeguards and training have been added following the event. Lire la suite

Amazon Web Services experienced two incidents involving its AI coding assistant Kiro, which were attributed to user error and permission issues rather than flaws in the AI itself. The first incident, described as an "extremely limited event" in mainland China, affected a single service, while the second had no impact on a customer‑facing AWS service. Following the incidents, AWS introduced mandatory peer reviews, staff training, and tighter access controls. The company continues to push for broader AI adoption among developers, targeting 80 percent usage at least once a week, while some employees remain skeptical of the technology’s overall utility. Lire la suite

Amazon Web Services introduced three new AI agents—Kiro, Security Agent, and DevOps Agent—designed to operate autonomously for extended periods. Kiro, a coding specialist, learns a team’s workflow, follows spec‑driven development, and can persist context across sessions. Security Agent independently identifies and proposes fixes for code vulnerabilities, while DevOps Agent handles testing and performance validation. AWS CEO Matt Garman highlighted the agents’ ability to take on complex backlog tasks with minimal human oversight, marking a significant step toward AI‑driven software development. Lire la suite