AWS Open-Sources AWS Emulator for 200+ Services
Contents
Running integration tests against cloud infrastructure usually means creating live resources and paying for API calls. To make offline testing practical, AWS released AWS Emulator, an open-source tool that serves a local HTTPS endpoint simulating the public APIs of more than 200 services.
The tool gives developers and autonomous coding agents a way to provision mock resources and catch realistic AWS error responses without touching remote accounts.
How AWS Emulator works
Written in Rust, AWS Emulator generates its endpoints from the 400+ Smithy API models that AWS maintains for its official SDKs. It works without edits to application code; you only need to redirect the SDK endpoint to the local port.
# Directing the AWS CLI or SDKs to the local emulator
export AWS_ENDPOINT_URL="http://localhost:4566"
aws s3 lsAWS provides prebuilt RPM and Debian packages for Linux on x86_64 and aarch64. macOS and Windows users can run it via Dockerfile instructions. Rust projects can also use an embedded mode, running the emulator inside the test process itself and passing its HTTP client straight to the AWS SDK for Rust.
Maintained by AI coding agents
The codebase is written and updated by autonomous AI agents running on Amazon Bedrock AgentCore Runtime Instances, AWS CodePipeline, and AWS CodeCommit. Three separate agent setups handle the workflow:
- Test generation agents: Write fidelity tests directly from public API models and verify them against live AWS accounts.
- Replay agents: Run those tests against the local emulator and open bug reports for discrepancies.
- Implementation agents: Write and commit the code patches that resolve those bug reports.
Every pull request must pass automated gates that check compilation, security rules, and regressions before merging into the main branch.
Fidelity rates and current limits
Feature parity depends on the service. Unimplemented operations return an HTTP 501 NotImplemented status. Published metrics indicate that Amazon S3, DynamoDB, and SQS pass roughly two-thirds of their fidelity suites, while CloudFormation currently passes fewer than one in five.
The emulator comes with deliberate boundaries:
- No IAM policy evaluation: It ignores identity-based and resource-based policies, so it cannot validate permissions.
- In-memory state: All data and created resources disappear when the process stops.
- Single-tenant scope: Each process runs against a single shared account and region, making it unsuitable for concurrency or load tests.
Ecosystem and licensing
Developers working offline have historically relied on tools like LocalStack, moto, and Floci. AWS Emulator differentiates itself by generating stubs straight from internal Smithy definitions and using a CC0 1.0 Universal (Public Domain) dedication for its original code. It is not an immediate substitute for full infrastructure-as-code or IAM testing, but it provides a lightweight foundation for local tests and automated agent pipelines.