AWS Open-Sources Emulator for Local Testing of 200+ Services by Coding Agents AWS released AWS Emulator, an open-source local program that serves an HTTPS endpoint emulating the public APIs of more than 200 AWS services, letting developers and coding agents create resources and hit the same errors AWS would return without provisioning cloud resources or incurring charges for emulated operations. Written in Rust and generated from more than 400 Smithy API models, the emulator was built by three agent teams running on Amazon Bedrock AgentCore Runtime Instances, AWS CodePipeline and AWS CodeCommit, with every change passing a merge gate for compilation, coding standards, security and fidelity regressions, according to AWS senior principal engineer Matthew Goldberg. AWS publishes versioned fidelity tests and per-service scores with each release, and documents limits including no evaluation of IAM or resource-based policies, a single shared account and Region per process, in-memory state that disappears when the process stops, and no testing for long-running use or load. AWS has released AWS Emulator https://aws.amazon.com/blogs/aws-insights/better-feedback-for-building-with-agents/ , a local program that serves an HTTPS endpoint for the public APIs of more than 200 AWS services https://www.allthingsdistributed.com/2026/11/aws-emulator-and-the-engineers-job-when-agents-write-the-code.html . AWS Emulator lets developers and coding agents create resources, hit the same errors AWS would return, and iterate without provisioning cloud resources or incurring service charges for the operations it emulates. Teams point the AWS CLI or an AWS SDK at it with environment variables such as AWS ENDPOINT URL https://docs.aws.amazon.com/emulator/latest/userguide/what-is-service.html , leaving application code unchanged. On Linux it installs as an RPM or Debian package for x86 64 or aarch64; on macOS and Windows, AWS documents a short Dockerfile https://aws.amazon.com/blogs/aws/test-your-applications-against-aws-locally-with-aws-emulator/ and does not publish a prebuilt image. Rust tests can use an embedded mode https://docs.aws.amazon.com/emulator/latest/userguide/getting-started-embedded.html that runs the emulator inside the test process and wires its HTTP client into the AWS SDK for Rust. An aws-emulator skill https://docs.aws.amazon.com/emulator/latest/userguide/getting-started-agent.html can start the emulator for coding agents and check a project against published fidelity tests. Written in Rust, it is generated from more than 400 Smithy API models https://github.com/aws/api-models-aws AWS publishes for the SDKs, according to Swaminathan Sivasubramanian. AWS says agents wrote and tested the code. Matthew Goldberg https://www.aboutamazon.com/news/aws/how-autonomous-ai-agents-built-aws-emulator , a senior principal engineer at AWS, describes three teams: one writes fidelity tests from the public API models and verifies them against real AWS, one replays those tests and files issues, and one implements each fix. Every change must pass a merge gate that checks compilation, coding standards, security, and fidelity regressions. The work runs on Amazon Bedrock AgentCore Runtime Instances https://aws.amazon.com/blogs/aws/test-your-applications-against-aws-locally-with-aws-emulator/ , AWS CodePipeline, and AWS CodeCommit. How closely the emulator matches AWS varies by service. AWS publishes versioned fidelity tests and per-service scores https://docs.aws.amazon.com/emulator/latest/userguide/fidelity.html with each release; a test passes only when every call matches AWS, including status codes, side effects, and exact errors. Unimplemented operations return HTTP 501 with the error code NotImplemented. AWS says fidelity is closest on control-plane APIs, while data-plane behavior and support for CloudFormation, Terraform, and the AWS CDK vary by service. Documented limits include no evaluation of IAM or resource-based policies https://docs.aws.amazon.com/emulator/latest/userguide/security.html , so it must not be used to test security; a single shared account and Region per process; in-memory state that disappears when the process stops; and no testing for long-running use or load. The evaluation suite https://github.com/aws/aws-emulator-evaluation-suite includes tests the emulator does not yet pass. Developers already have several local AWS stand-ins, including LocalStack https://www.localstack.cloud/ , Floci https://floci.io/ , and moto https://github.com/getmoto/moto . AWS Emulator is generated from AWS's own API models, ships official fidelity scores, and is dedicated to the public domain, but it is not a drop-in replacement for every workflow those tools cover, especially permission testing and infrastructure-as-code pipelines. Developer Josh Builds https://x.com/Joshua WD/status/2120737306176897144 wrote: AWS just released a free local emulator of its APIs, made for coding agents and written entirely by agents. I counted its published fidelity tests: S3, DynamoDB and SQS pass about 2 in 3. CloudFormation passes under 1 in 5. Yurii Serhiichuk https://x.com/xSAVIKx/status/2120660859353506105 compared it with existing emulators and published a container image and GitHub Action https://serhiichuk.dev/blog/aws-emulator-container-image/ to cover a packaging gap: AWS shipped AWS Emulator today - think LocalStack/Floci but native. Rust, built by agents so hopefully it gets updated pretty fast . No public docker image though, and no GitHub action. So I filled that part. AWS Emulator is generally available at no additional service fee. Source is on GitHub https://github.com/aws/aws-emulator under the CC0 1.0 Universal public domain dedication, except third-party code in the vendor/ directory, which is under the Apache License 2.0. Setup details are in the user guide https://docs.aws.amazon.com/emulator/latest/userguide/what-is-service.html , and fidelity scores https://github.com/aws/aws-emulator/releases ship with each release.