Let your coding agent hammer a fake AWS instead of your real one
AWS's own open-source emulator fakes 200+ services locally, so agent mistakes cost nothing.
AWS Emulator is a local HTTPS endpoint that answers the public APIs of more than 200 AWS services. Point your coding agent at it and a botched deploy hits a clone, not your account or your bill.
The deeper look
The case for it is simple. Agents retry a lot, and retries against real infrastructure create real resources and real charges. A local clone makes the loop cheap and safe. Simon Willison tried it hands-on and covered it the day it appeared. InfoQ covered the launch too.
The limits come from AWS's own documentation, so treat them as reliable. Fidelity is closest on control-plane APIs, and AWS ships published fidelity scores with each release. State lives in memory, each process serves one account and one Region, and load testing is out. The biggest one: no IAM or resource-policy evaluation, so a test passing here says nothing about whether your permissions are right.
That makes it a fit for builders who want agents to iterate on application logic. Skip it for security checks, performance tests, or anything that depends on a service the fidelity page marks weak.
How to start: clone github.com/aws/aws-emulator, run it, and set your SDK's endpoint to the local address. Read the fidelity page in the AWS docs before trusting a given service.
$ git clone https://github.com/aws/aws-emulator