AWS Emulator: free local AWS for 200+ services, built by AI agents
AWS Emulator runs 200+ AWS service APIs on your machine for free under CC0. AI agents wrote all of it. Cut cloud test costs, but don't test security with it.
AWS just gave you a free copy of its cloud to test against, and no human wrote a line of it. AWS Emulator, released November 11, runs the AWS APIs on your own machine, a dev server or CI. GeekWire reports it is built from more than 400 API models covering more than 200 AWS services. It is free, needs no AWS account, and the code is public domain. For a small team paying for every test run in the cloud, that is a real line item you can delete.
What actually happened
- How it works. The emulator serves an AWS API endpoint locally. You set environment variables to point the AWS CLI or SDK at it and run your code unchanged, per the README. Linux gets RPM and Debian packages. Windows and macOS run it in Docker. Rust projects can embed it in-process, one instance per test.
- Who wrote it. "The emulator was written entirely by autonomous agents. Our team hasn't written or reviewed any of the code," AWS senior principal engineer Matt Goldberg wrote. Agents on Amazon Bedrock AgentCore work in three teams: one writes fidelity tests against real AWS, one runs them against the emulator and files failures, one fixes them. Other agents gate every merge for standards and security.
- License and price. CC0 1.0, except the
vendor/folder (Apache 2.0). No service fee. GeekWire notes LocalStack put its free tier behind an account this year and limited it to noncommercial use. - Limits. AWS says not to use it for production or to test security. An IDC analyst told InfoWorld it doesn't yet simulate throttling, outages or regional feature differences. Known gaps sit in a public
issues/things-that-do-not-work/folder. - Telemetry. It is on by default. Turn it off with
--telemetry offorEMULATOR_TELEMETRY=off.
Why it matters for your business
Coding agents test by running code over and over. Against real AWS, each loop costs time and money. A local endpoint makes that loop cheap and fast, for your developers and for agents like Claude Code.
How we would roll it out:
- Start in CI. Point one integration suite at the emulator. Compare results to a nightly run against real AWS.
- Check fidelity first. Each release publishes per-service fidelity scores. Read them for the services you actually use.
- Keep IAM and security tests on real AWS. Permissions are where "passes locally" can lie to you.
- Turn telemetry off in shared CI images, and tell your team.
Key takeaways
- AWS Emulator runs 200+ AWS service APIs locally, free, no AWS account needed
- AI agents wrote and maintain all of the code; AWS engineers did not review it
- Licensed CC0 (vendor folder Apache 2.0) on GitHub at aws/aws-emulator
- Not for production or security testing; throttling and outages aren't simulated yet
- Telemetry is on by default: set EMULATOR_TELEMETRY=off in CI
Paying AWS to run your test suite? We set up CI pipelines that test locally first and hit the real cloud only where it matters, so your agents and developers ship faster for less. See what we build or estimate your savings.
Sources: GeekWire, AWS Emulator on GitHub.
- #aws-emulator
- #aws
- #local-testing
- #ci
- #ai-coding-agents
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
ScreenConnect attacks hit MSPs: rogue clients on 286 endpoints
Attackers used hijacked ScreenConnect accounts to push rogue remote clients through MSPs. ConnectWise disabled five extensions. Ask your MSP these questions.
Read itRailway stolen AI keys: $740K spend, and who refunds what
Railway's final incident report puts unauthorized spend on stolen AI API keys at ~$740,000. AWS and Google refund fraud, OpenRouter won't. Set spend caps now.
Read it