AWS ships an emulator it says no human wrote or reviewed

AWS Emulator runs on a developer's machine and answers AWS API calls so software can be tested without an AWS account. Goldberg writes: "The emulator was written entirely by autonomous agents. Our team hasn't written or reviewed any of the code." He describes three teams of agents. The first writes fidelity tests from the public AWS API models and verifies each one against real AWS before submitting it. The post puts the suite at "tens of thousands" of tests. The second team replays those tests against the emulator and files issues for the failing tests, grouping failures that may share a root cause. In the third, one agent takes one issue, fixes it, and submits the change to a merge gate. The gate rejects code that does not compile, runs review agents for coding standards and security, and checks that fidelity did not regress. A failed change goes back to its agent for rework. Goldberg says hundreds of agents work on the codebase at once and fix thousands of issues a day, and adds: "Without this merge gate, we wouldn't trust what our agents are building."

The repository is public under CC0 and showed 29,684 commits when we looked on the afternoon of November 11. Its README says the emulator is for building and testing, not for production workloads or security testing, and that the repository does not take pull requests. Open and fixed issues sit in two folders, issues/things-that-do-not-work and issues/things-that-now-work. The repository's AGENTS.md marks the vendor/ directory as an "agent-immutable framework".

In a companion post on Werner Vogels's All Things Distributed, AWS's Swami Sivasubramanian says the engineer's job is now "to build the specs, tests, and merge gates that decide when that work is correct." He gives one comparison from his own work. He used Kiro to rebuild a replication engine that first took about four months to write, and supervised the agent for four nights before he saw that "it had no way to check its results." With a spec and a test environment, he writes, "the rebuild took about two hours." The Hacker News thread on the repository had 405 points and 125 comments 2.7 hours after posting.

Both posts are AWS's own account, and neither gives a fidelity score or a defect rate. The claim that no person reviewed the code cannot be checked from outside. Goldberg calls his post the first in a series that will cover how the team measures fidelity and holds its security bar.

Why it matters: This is a vendor shipping a public codebase and saying in writing that the gate, not a person, decides what merges. The setup depends on two things most projects lack: a machine-readable spec for every operation, and a real system to test against. Goldberg names both as the reason he tried it. Teams weighing a no-review pipeline should ask first whether they have an equivalent of those two, and note what the product is: a test tool that AWS says not to use for production workloads or security testing.