AWS released AWS Emulator, a local copy of more than 200 AWS services whose code was written entirely by agents
AWS released a local emulator of its own cloud on 11 November, and says every line of its code was written by autonomous agents. The human team, AWS says, has not written or reviewed any of it.
AWS Emulator is a program you run on your machine, or in Docker, so the AWS CLI, the SDKs and coding agents can call AWS APIs without an AWS account and without a deployment. AWS says it is built from more than 400 API models covering more than 200 AWS services. There is no extra service fee. The source is on GitHub under CC0, a dedication to the public domain. At launch it does not evaluate IAM policies, which are the access rules AWS uses, the way the real cloud does, and each copy acts as a single account.
Why this one is different
Local AWS stand-ins have existed for years. The unusual claim is how this one was built. AWS describes three teams of agents: one writes fidelity tests from public API models and checks them against real AWS, one finds where the emulator diverges, and one fixes those gaps. A merge gate blocks a change that does not compile, fails a security review, or reduces fidelity. Swami Sivasubramanian, writing on Werner Vogels's blog, says an engineer built the scaffolding, and that the agents wrote and tested all of the code.
More than 200 services, and a human team that says it did not write the code.
How we got here
- Early careerAn AWS engineer, Matt Goldberg, tests the idea on Amazon SQS. He says Kiro, Amazon's coding agent, returned a first SQS emulator in about 15 minutes.
- A weekendAn internal version comes together and starts to be used within a month, according to Swami Sivasubramanian.
- 11 Nov 2026AWS releases the emulator, with the agent commit history public, and a folder for behaviours that do not yet match AWS.
What it does and does not mean
A claim that agents wrote every line is AWS's account of its own process, and it is not an independent audit. The product also does not claim to be a complete stand-in: IAM is not evaluated as in AWS, cross-account and cross-Region behaviour are absent, unsupported operations return 501, and AWS tells you to test security on AWS before production. What the launch does establish is a free, local endpoint covering a large fraction of the public AWS API surface, maintained by a test loop against the real cloud. How close that loop stays is a question for the fidelity report, not for the announcement.