All postsSHORT2 min read
AWS Says Agents Wrote All of AWS Emulator, Without Human Code Review
AWS Emulator runs 200+ AWS services locally for free. AWS says agents wrote all its code. Here's how to try it and where IAM checks fall short.
Free AWS on your laptop. AWS released AWS Emulator on November 11, 2026. It covers more than 200 AWS services, and AWS says autonomous agents wrote every line of code. Its team hasn't written or reviewed any of it, according to AWS.
What it is
AWS Emulator gives you a local copy of AWS services for building and testing applications. It runs free and offline, without an AWS account. The emulator code is released under CC0, a public domain dedication, except code in the vendor/ folder, which is under the Apache License 2.0.
You can point the AWS CLI and SDKs at the emulator through environment variables. Your application code doesn't change. The user guide lists integration tests in CI/CD as a use case, with no AWS account or AWS resources in that pipeline.
How agents built it
AWS says Kiro produced a passable first SQS emulator in about 15 minutes from one prompt.
AWS says it uses three teams of agents: one manages tests, another finds gaps, and another fixes issues. AWS says agents check tests against real AWS before submitting them. A merge gate includes security-review agents.
AWS says the project has tens of thousands of fidelity tests. That still comes with limits on what the emulator can prove about your app.
How to try it
Start with the repo and user guide.
For agent setup, you'll need AWS CLI 2.35.0 or later. The agent guide gives this command:
aws agent-toolkit add-skill --skill-name aws-emulator --region us-east-1
It installs the skill for coding agents the CLI finds on your machine, such as Kiro, Cursor and Claude Code. Then ask your agent to install AWS Emulator and point your project at it.
On Linux, the guide uses an RPM or Debian package. On macOS and Windows, you run it in Docker using an image you build with the project's Dockerfile.
Telemetry is on by default. You can turn it off with --telemetry off or EMULATOR_TELEMETRY=off.
The catch
AWS says don't use the emulator to test security. It doesn't evaluate IAM and resource-based policies the way real AWS does. A request AWS denies might succeed locally, and one AWS allows might fail. Passing local tests doesn't prove your permissions are safe.
Run security checks and test your whole app on real AWS before production.
Fidelity also varies by service. AWS says control-plane APIs are the closest match. An operation that hasn't been implemented returns HTTP 501 with NotImplemented.
Keep this to test runs. Resources live in memory and disappear when the emulator stops. AWS says it hasn't tested long-running use or load testing, and says don't use it for production workloads. Don't use real AWS credentials or real customer data. Function code runs without isolation from your machine.
The builder angle (my opinion, no income guaranteed)
I'd sell small AWS teams an agent-ready integration test setup. Configure their CI and coding agents to test against the emulator, then keep security and permission checks on real AWS.
The deliverable: a working integration test pipeline, agent setup, and a separate real-AWS security check before production. That's the service I'd offer.
Daily email
Get each breakdown in your inbox.
One email each evening, right after the Short goes live: the AI tool it covers, the full write-up with sources, and how to get paid for it. Free, and you can unsubscribe anytime.