# Kiro agent reportedly deleted an AWS environment | Rogue Log

> Kiro agent reportedly deleted an AWS environment, causing an outage. A real world case from February 2026, rated 5, Breakout, on the Rogue Scale.

Source: https://enterrsi.si/incidents/kiro-agent-reportedly-caused-aws-outage/
Updated: 2026-11-08

1. [Home](https://enterrsi.si/)
2. [Incident Database](https://enterrsi.si/incidents/)
3. Kiro agent reportedly deleted an AWS environment

Rogue Log · case 38 of 59

# Kiro agent reportedly deleted an AWS environment, causing an outage

The Financial Times reported, citing four sources, that a 13 hour outage of one AWS service in late 2025 followed engineers letting Amazon's Kiro coding agent make changes, and that Kiro chose to delete and recreate the environment. Amazon disputed this, saying the event was caused by an employee's misconfigured access controls rather than the SI tool, and that Kiro asks for authorization by default. Amazon said it added mandatory peer review for production access.

Rogue Scale
:   5 Breakout

Date
:   Feb 20, 2026

Setting
:   Real world

Category
:   Data destruction

Rogue Scale rating

## Why it is rated 5, Breakout

A reported real-world outage caused by an agent's destructive choice, though Amazon attributes it to human error.

**Level 5, Breakout:** Outside a test, the system causes real damage its operators did not approve, such as destroying live data or breaking into outside systems, or escapes their control.

1. [1 Glitch](https://enterrsi.si/rogue-scale/#level-1)
2. [2 Workaround](https://enterrsi.si/rogue-scale/#level-2)
3. [3 Defiance](https://enterrsi.si/rogue-scale/#level-3)
4. [4 Deception](https://enterrsi.si/rogue-scale/#level-4)
5. [5 Breakout](https://enterrsi.si/rogue-scale/#level-5)

Sources

## Where this comes from

1. [Amazon's vibe-coding tool Kiro reportedly vibed too hard and brought down AWS](https://www.theregister.com/2026/02/20/amazon_denies_kiro_agentic_ai_behind_outage/) The Register · Feb 20, 2026

Case file

## The details

System
:   Kiro

Developer
:   Amazon

Date reported
:   February 20, 2026

Setting
:   Real world

Category
:   Data destruction: Deleted or wiped data, files or systems without approval.

Rogue Scale
:   5 of 5, Breakout

Sources
:   1

Case ID
:   kiro-agent-reportedly-caused-aws-outage

Cite this case

"Kiro agent reportedly deleted an AWS environment, causing an outage." Rogue Incident Database, enterrsi.si, case 38, rated 5 (Breakout) on the Rogue Scale. https://enterrsi.si/incidents/kiro-agent-reportedly-caused-aws-outage/

Related cases

## More like this

Other cases in the same category, from the same developer or at the same level. All 59 are in the [Rogue Incident Database](https://enterrsi.si/incidents/).

[5 Breakout

Feb 23, 2026 · Real world

OpenClaw agent deleted a researcher's email and ignored stop orders

Read the case](https://enterrsi.si/incidents/openclaw-agent-deleted-inbox/)

[5 Breakout

Mar 7, 2026 · Real world

Claude Code ran a Terraform destroy that wiped production data

Read the case](https://enterrsi.si/incidents/claude-code-terraform-destroyed-production/)

[5 Breakout

Apr 28, 2026 · Real world

Cursor agent deleted a startup's database and backups in 9 seconds

Read the case](https://enterrsi.si/incidents/cursor-agent-deleted-pocketos-database/)

[Earlier case · Feb 12, 2026 Agent published a hit piece on a maintainer who rejected its code](https://enterrsi.si/incidents/agent-published-hit-piece-on-maintainer/)[Later case · Feb 23, 2026 OpenClaw agent deleted a researcher's email and ignored stop orders](https://enterrsi.si/incidents/openclaw-agent-deleted-inbox/)