AWS has released AWS Emulator, a free local implementation of more than 200 of its services dedicated to the public domain under CC0, and says that "thousands of autonomous AI agents wrote every line of code" in it. As InfoQ reported at launch, it ships as a single Rust binary generated from AWS's 438 public API models and listens on port 9297. The week since has brought the first independent fidelity numbers and a divided practitioner reaction.
Pointing an existing SDK, CLI, or coding agent at the emulator is a matter of environment variables, after which the launch post by Daniel Abib says, "your existing tests, CLI scripts, and coding agents keep working the way they already do":
export AWS_ENDPOINT_URL=https://127.0.0.1:9297
export AWS_SHARED_CREDENTIALS_FILE=~/.aws/emulator/9297/emulator_credentials
export AWS_CONFIG_FILE=~/.aws/emulator/9297/config
export AWS_EC2_METADATA_DISABLED=true
export AWS_REGION=us-east-1
unset AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY AWS_SESSION_TOKEN AWS_PROFILE
The same shell serves an agent. In the post, Kiro is asked to create and read back a DynamoDB table and issues the ordinary CLI calls against the local endpoint:
kiro> Using the local AWS Emulator (the environment variables
are already set in this shell), create a DynamoDB table
"kiro-demo" with a string key "id", put an item
{id: "item-1", msg: "hello from kiro"}, then read it
back with get-item.
$ aws dynamodb create-table --table-name kiro-demo \
--attribute-definitions AttributeName=id,AttributeType=S \
--key-schema AttributeName=id,KeyType=HASH \
--billing-mode PAY_PER_REQUEST
$ aws dynamodb put-item --table-name kiro-demo \
--item '{"id": {"S": "item-1"}, "msg": {"S": "hello from kiro"}}'
$ aws dynamodb get-item --table-name kiro-demo --key '{"id": {"S": "item-1"}}'
Matt Wood, AWS's chief AI and technology officer, argues that the loop matters because of what an agent does while a check is slow: "A coding agent can build a lot of software around an incorrect assumption." He also names the failure mode an emulator introduces:
An agent learns from the environment it experiences. If the emulator accepts behavior that AWS rejects, training can reinforce a mistake. An agent might also discover a shortcut that succeeds only because of an emulator defect.
The fidelity scores exist to expose that gap: each release publishes per service how many tests pass out of how many were verified against real AWS, with the failing tests public too, and Abib asks readers to "read a score as a snapshot of a product that's improving."
Senior principal engineer Matthew Goldberg traces the project to a three-line prompt given to Kiro, "the simplest prompt that I could think of without any expectation that this would work":
Write tests based on the AWS Command Line Interface (CLI)
Iterate on those tests until they pass against real AWS
Build an in-memory implementation that those same tests pass against
Kiro came back after 15 minutes with a passable first version of an Amazon Simple Queue Service (Amazon SQS). I refined my prompt and had Kiro build me the rest of AWS over the weekend. And it did. It obviously had gaps, but it was compelling enough that my team started using it to test our software that Monday.
The production version is built by three agent teams: "One team manages a test suite; one team finds issues in the emulator; and one team fixes those issues." Each fix must pass a gate that compiles the change and runs agent reviews for coding standards, security, and fidelity regression. "Our team hasn't written or reviewed any of the code," Goldberg writes, and describes what the gate carries:
If any of those checks fail, the change is sent back to the agent for rework; if they all pass, it is merged to mainline. We've seen thousands of issues fixed every day as hundreds of agents concurrently work on the codebase. Without this merge gate, we wouldn't trust what our agents are building.
Swami Sivasubramanian, in a guest post on Werner Vogels' blog, recalls rebuilding a replication engine with Kiro that had taken his team four months by hand:
I supervised the agent for four nights before I saw that it had no way to check its results. Once it had a spec and a test environment, the rebuild took about two hours
In his telling, the engineer's job becomes "to build the specs, tests, and merge gates that decide when that work is correct."
The first measurements from outside AWS come from Kento Ikeda, an AWS Community Builder, who ran version 1.0.322 in GitHub Actions the day after launch. DynamoDB, S3 and SQS passed roughly 60 to 70 percent of their fidelity tests at service level and 80 to 100 percent on the operations its code called, while CloudFormation sat near 20 percent. The emulator matched AWS's error wording, but a new DynamoDB table stayed in CREATING for three seconds and rejected writes until then. "Being generated from API models only means the shape of requests and responses matches AWS," he writes, and places the tool between mocks and a real sandbox as a third layer rather than a replacement for either.
The launch post draws its hardest line at security:
Don't use the emulator to test whether your application is secure. It doesn't evaluate AWS Identity and Access Management (IAM) policies and resource-based policies the way AWS does, so a request that AWS denies might succeed in the emulator. Keep real credentials out of the environment of your test jobs, and test your security settings and your whole application on AWS before you go to production.
Unimplemented operations return HTTP 501, telemetry is on by default, throttling, outages and regional differences are not simulated, and the repository does not accept pull requests. On Hacker News, one reader quoted the line on the security page that the emulator "never denies a request signed with its own key" and asked why IAM was left out:
I think because the agents were only building on the public API surface, it's hard to build this part. But they should've tried and let the agents read whatever policy engines AWS has. Or maybe it's a way to prevent someone from trivially running aws-emulator as AWSaaS?
The thread's first question was whether this was "just an exercise or a real product they are going to ship and maintain," answered by a commenter identifying as AWS staff with "It's a real product that we plan to maintain." Another counted "29,684 commits in a repository less than a month old" and said it "does not instill confidence." On r/aws, the most-upvoted comment turned Amazon's own line around, calling agents that fix code "without human review" a terrible idea for a tool used to test before production. The reply was that the API specifications already exist and the SDKs are generated from them, so a server derived from a fixed contract is where agents can iterate until the tests pass.
The timing matters to the people in those threads. LocalStack's free Hobby plan now requires an account and prohibits commercial use, with paid seats from $39 a month, and several commenters had already moved to Floci. One of them put the AWS release in that context:
But in the wake of Localstack's changes, the landscape has been full of slopware and low trust anyway. I don't think this is worse, for now at least.
AWS's version costs nothing and can be forked by either project. Sivasubramanian says AWS "will share more about this work at re:Invent" in December.