Amazon says an AI caused a December incident. The fix is a form.

Amazon disclosed this month that a December incident in its infrastructure was caused by an AI system's actions, per incident tracking coverage, and announced safeguards to follow: mandatory peer review for AI-initiated production changes and tightened permission controls for automated actors.

Two details deserve more attention than the headline. First, the timeline: the incident occurred in December and the disclosure arrived in February, which is a normal interval for a postmortem and an eternity for an industry currently deciding how much autonomy to grant AI operators. Second, the shape of the fix. Mandatory peer review is the oldest control in software engineering, and applying it to machine-initiated changes is an admission with a precise meaning: the AI actor is now treated as an engineer, with an engineer's failure modes and an engineer's supervision.

The pattern will be familiar to anyone who has read this winter's outage cluster reporting: configuration change remains the leading cause of major incidents, and it does not much matter whether the hands on the config were human. The permission system that could not stop a bad human change could not stop a bad automated one either.

The builder's read: if your organization is wiring agents into production workflows, Amazon just published the control baseline for free. Review gates and least-privilege for automated actors, before the incident, not in the February after it.