AWS Emulator: Agent-Built, Free, Local, 200+ Services

Published • news
AWSAI AgentsDeveloper Tools

AWS Emulator, announced by AWS on 11 November 2026, is a free CC0-licensed local implementation of more than 200 AWS services. InfoQ's Steef-Jan Wiggers reports that AWS says thousands of autonomous AI agents wrote every line. Daniel Abib's launch post positions it as the AWS CLI, SDKs, and coding agents speaking to a laptop endpoint through the same APIs they use in the cloud, with no additional service fee and application code unchanged.

An agent-built pipeline

AWS senior principal engineer Matthew Goldberg says the project began with a three-line Kiro prompt: write tests from the AWS CLI, iterate until those tests pass against real AWS, and build an in-memory implementation that passes the same tests. Kiro returned a passable Amazon SQS in 15 minutes; after refining the prompt, Goldberg says it built "the rest of AWS over the weekend." Production now uses three agent teams: one owns a test suite, one finds emulator issues, and one fixes them. Each fix passes 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; hundreds of agents working concurrently fix thousands of issues per day.

Swami Sivasubramanian gives the same loop a different scale: rebuilding a replication engine that took his team four months by hand took about two hours once the agent had a spec and test environment. He casts the engineer's job as building the specs, tests, and merge gates that decide when work is correct.

Local execution modes

On Linux, aws-emulator installs from an RPM or Debian package; on macOS and Windows you build a Docker image from the documentation's Dockerfile. At startup it writes credentials, config, and certificate under ~/.aws/emulator/9297/, listens on 127.0.0.1:9297, uses account 000000000000, and emits access key IDs prefixed with EMULATOR. The CLI or an SDK points at it via endpoint and credential environment variables.

AttributeProcess modeEmbedded mode
DistributionRPM/Debian on Linux; Docker image on macOS and WindowsRust crate in [dev-dependencies] from GitHub
TransportLocal HTTPS endpoint at 127.0.0.1:9297In-process SDK HTTP client
State isolationOne shared emulator state per serverPer-instance state; parallel tests do not share buckets, tables, or queues
SDK reachAWS CLI plus SDKs via environment variables; some SDKs need a certificate trust storeAWS SDK for Rust

Fidelity and security boundaries

AWS publishes per-service fidelity scores for each release—how many tests pass out of how many were verified against real AWS—with failing tests public. Abib asks readers to treat a score as "a snapshot of a product that's improving." Matt Wood warns that an agent learns from the environment it experiences: if the emulator accepts behavior AWS rejects, training can reinforce a mistake or reward an emulator-only shortcut.

Kento Ikeda, an AWS Community Builder, ran version 1.0.322 in GitHub Actions the day after launch. In his measurements, DynamoDB, S3, and SQS passed roughly 60 to 70 percent of service-level fidelity tests and 80 to 100 percent of operations his code called, while CloudFormation sat near 20 percent. Error wording matched AWS, but a newly created DynamoDB table stayed in CREATING for three seconds and rejected writes until then. Ikeda places the tool between mocks and a real sandbox.

AWS is explicit that the emulator is not a security test: it does not evaluate IAM or resource-based policies the way AWS does, so a request AWS would deny might succeed locally. 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.

AI Mastery analysis

Shape fidelity is the easy part. Because the emulator is generated from the same 438 public API models as the SDKs, request envelopes, error wording, and parameter validation can match AWS. The hard part is what those models do not encode: state transitions, IAM evaluation, resource policies, throttling, and regional variation. Ikeda's CloudFormation result near 20 percent is the clearest evidence, since orchestration semantics are cross-service and time-dependent.

That gap is a shared-surface problem, not a model-logic problem: shared surfaces rather than model logic get exercised differently without an account boundary or IAM engine. An agent that succeeds locally may learn an assumption that only holds in the emulator, and the security page's statement that the emulator "never denies a request signed with its own key" means the local environment cannot approximate least-privilege behavior. The agent-maintained merge gate is credible because the API contract is fixed, but one Hacker News commenter counted 29,684 commits in a repository less than a month old, and AWS says no human reviewed the code. That makes auditability and regression discipline the real test.

InfoQ reports that LocalStack's free Hobby plan now requires an account and prohibits commercial use, with paid seats from $39 per month. AWS costs nothing and publishes its own failing tests; Sivasubramanian says AWS will share more at re:Invent in December. The signal is not that local emulation is new, but that a vendor with the actual API models can ship a CC0, forkable emulator and publish its failing tests, making fidelity measurable rather than assumed.

Sources

Frequently asked questions

How much does AWS Emulator cost?

AWS Emulator is free and CC0-licensed. There is no additional service fee, and AWS says you pay only for AWS resources when you later deploy on AWS.

Does AWS Emulator run on a single laptop?

Yes. On Linux it installs from an RPM or Debian package, while macOS and Windows users run it in Docker. It listens on 127.0.0.1:9297 and uses the single AWS account 000000000000.

What fidelity scores did early AWS Emulator tests show?

Kento Ikeda ran version 1.0.322 in GitHub Actions and reported DynamoDB, S3, and SQS passing roughly 60 to 70 percent of service-level fidelity tests and 80 to 100 percent of operations his code called. CloudFormation sat near 20 percent.

Can AWS Emulator test IAM security policies?

No. AWS says the emulator does not evaluate IAM or resource-based policies the way AWS does, so a request AWS would deny might succeed locally. Unimplemented operations return HTTP 501.

Who wrote AWS Emulator's code?

AWS says thousands of autonomous AI agents wrote every line. Senior principal engineer Matthew Goldberg says the project began with a three-line Kiro prompt, and the production system is built by three agent teams behind a merge gate that compiles changes and runs coding, security, and fidelity reviews.

Free interactive tools for the decisions this piece raises.

Related Reading