# AWS releases open-source local emulator for 200+ services, built for coding agents

published: 2026-11-16T11:05:24.355Z
topic: infrastructure
source: https://www.infoq.com/news/2026/11/aws-emulator-agents/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AI%2C+ML+%26+Data+Engineering
url: https://aiagentnews.io/stories/aws-releases-open-source-local-emulator-for-200-services-built-for-coding-agents

AWS has released AWS Emulator, a local program that serves an HTTPS endpoint for the public APIs of more than 200 AWS services. Developers and coding agents can test against it without provisioning cloud resources or paying for the operations it emulates.

Teams point the AWS CLI or an AWS SDK at the emulator using environment variables such as AWS_ENDPOINT_URL, so application code stays unchanged. On Linux it installs as an RPM or Debian package for x86_64 or aarch64, while macOS and Windows users are pointed to a Dockerfile. Rust tests can run it embedded inside the test process, and an aws-emulator skill lets coding agents start it and check a project against published fidelity tests.

The emulator is written in Rust and generated from more than 400 Smithy API models that AWS publishes for its SDKs. AWS says agents wrote and tested the code, with each change passing a merge gate that checks compilation, coding standards, security and fidelity regressions.

Fidelity varies by service. AWS publishes versioned fidelity tests and per-service scores, and unimplemented operations return HTTP 501 with the error code NotImplemented. Documented limits include no evaluation of IAM or resource-based policies, a single shared account and Region per process, in-memory state, and no support for long-running or load testing.

## Why it matters if you build agents

Agents can exercise AWS API calls locally and get the same error responses AWS would return, which can make iteration faster and cheaper during development.

Do not use it to test security or permissions, since IAM and resource-based policies are not evaluated. Check the per-service fidelity scores before relying on CloudFormation, Terraform or CDK workflows, which AWS says vary by service.

Compared with LocalStack, Floci and moto, AWS says it is not a drop-in replacement for every workflow those tools cover.
