AWS launches official Rust emulator to test services without paid credentials

The aws-emulator runs a local clone of AWS services for integration testing, doing away with the need for paid API keys. It was written by a swarm of AI agents and, for now, only works with Docker.

Editor's note: this article cites LocalStack as a tool that has simulated AWS services "for years" and would be a "de facto standard among many teams." This claim does not appear in the source used for this report (Simon Willison's post) and could not be independently verified before publication. Treat it as general market context, not as data checked by this editorial team.

AWS released aws-emulator, described by developer Simon Willison on his blog on November 11, 2026, as the company's first official emulator for running tests against a local clone of its many services, without needing to provision a paid API key for that. It's a project that directly tackles a well-known problem for those who write integration tests against the cloud: the cost (in money and in credential bureaucracy) of hitting real services just to validate code.

The software is written in Rust, and its origin was told by Swaminathan (Swami) Sivasubramanian, of AWS, in a guest post on Werner Vogels's blog. Willison doesn't reproduce the content of that post, but highlights a number he considered noteworthy: the project's pace of creation.

A swarm of agents wrote the code

The most striking detail of the launch isn't what aws-emulator does, but who wrote the code behind it. According to Willison, the project was built by a huge number of AI agents working in parallel, not by a traditional team of human engineers typing line by line.

It's written in Rust by a huge swarm of agents - 29,684 commits in the first three weeks of the project.

Simon Willison, developer and author of the blog simonwillison.net

That's more than 1,400 commits a day, on average, over a three-week period. That doesn't say anything about the quality of the code by itself, but it says a lot about how willing AWS is to trust agentic pipelines to generate and validate critical test infrastructure. It's a concrete data point for anyone following the agentic engineering movement: a big tech company putting its name on a product mostly written by agents, not as a blog post experiment, but as an official testing tool.

Today's limitation: it still needs Docker

In the current version, aws-emulator depends on Docker to run on macOS or Windows. Willison notes this as the project's main gap and expresses hope that AWS will solve the problem in the future, allowing a single binary to be downloaded and used in other languages and platforms without this extra dependency.

This caveat matters in practice. Teams that already use Docker in CI pipelines won't feel the friction, but squads that run test suites on machines without Docker configured (or on leaner runners to save CI minutes) gain one more piece of infrastructure to keep alive just to run tests.

What changes for those testing integration from Brazil

Before aws-emulator, solving this problem locally was already possible with third-party tools, such as LocalStack, which has simulated AWS services for testing purposes for years and has become a de facto standard on many teams. The difference now is having an option maintained by AWS itself, which tends to reduce the gap between the emulator's behavior and that of the real API, since whoever writes the production service and whoever writes the emulator are now, at least in part, on the same side.

This changes the math for anyone building integration test pipelines on a small team. Today, running tests against S3, DynamoDB, or other AWS services in CI usually requires one of two paths: provisioning credentials for a real test environment (with usage costs and the risk of leaking a secret in a pipeline log) or keeping a third-party emulator manually updated with every API change. An official emulator reduces the second risk, because maintenance becomes the responsibility of whoever defines the original API.

For freelancers and smaller squads in Brazil, who feel the cost of API calls in a test environment more than a big tech company would, this has a direct effect on the CI budget. Integration tests that today run against a paid real environment (or against a limited sandbox) can now run locally, for free, as long as the machine has Docker available.

What still can't be answered

The source doesn't list which AWS services are already covered by the emulator, nor under which license the project was published. Also, as of the publication of Willison's post, there's no confirmation of guaranteed compatibility with the official AWS SDKs for each language, nor a public roadmap for when (or whether) the Docker dependency goes away.

It's worth following the project's repository and the agentic-engineering tag on Willison's blog for updates, because the commit pace suggests aws-emulator's surface could change fast in the coming weeks. For anyone deciding today between keeping a third-party emulator or migrating to the official option, the prudent move is to test it on a non-critical project before swapping out the main test suite.