# AWS Emulator: Test Your AWS APIs Without Waiting for Deployment

> An agent spent four nights rebuilding a service, then about two hours with a specification and a test environment. AWS Emulator lets you check interactions with AWS APIs locally, without waiting for a cloud deployment.

By Anthony Carbonnier, DevOps / SRE · Cloud architect
Published on November 17, 2026, updated on November 19, 2026
Topics of the article : AWS Emulator, AWS, Agents de code, Tests, IA
Web version: https://metanaps.com/en/blog/aws-emulator-testez-vos-applications-aws-en-local-sans-deploiement/

## Key takeaways

- AWS Emulator tests AWS APIs locally, without a cloud deployment.
- It supports modeled APIs; The New Stack mentions more than 200 services.
- In the example cited, a rebuild goes from four nights to about two hours with a specification and a test environment.
- The emulator replaces neither tests for internal services nor pre-production checks.

An agent spent four nights rebuilding a service. With a specification and a test environment, it took **about two hours**. According to AWS, the difference comes down to one detail that changes everything: the agent could finally check its work. AWS Emulator lets you test interactions with AWS services locally, without deploying to the cloud.

## Test AWS without leaving your machine

The emulator runs on your machine and exposes a local HTTPS endpoint. You can send it requests using the AWS CLI, SDKs, or coding agents, with the usual AWS APIs. Your existing applications and tests can stay as they are. For example, a test that creates a DynamoDB table, writes an item to it, then reads it back can also run locally.

AWS relies on its public API models, the same ones used by the SDKs. The company says this means requests and errors have the same shape as they do on AWS. The emulator supports APIs for services with a model in the public API models repository. The New Stack mentions **more than 200 services**. That's quite a crowd.

## There's one little catch with the installation

On Linux, you need an RPM or Debian package. On macOS or Windows, you need a Docker container. **AWS doesn't provide a ready-to-use Docker image.** At startup, the emulator generates credentials, a configuration file, and a certificate in `~/.aws/emulator/9297/`. You then configure your tools to point to the local endpoint.

AWS says there are no additional service fees. Resources are still billed when you deploy them on AWS. In short, local testing saves you from waiting for deployment, not from the bill once you're in production...

## An agent needs to be able to correct itself

A coding agent works through successive attempts: it writes, runs, checks the result, and fixes things. If its environment doesn't reproduce the behavior of the services it calls, it can mistake an error for success, or vice versa. Testing AWS APIs locally gives it feedback without waiting for a deployment to a region. Much better than discovering the problem afterward!

Swami Sivasubramanian's account offers a striking example. Building the first version of a replication engine would have taken about four months. Later, he asked Kiro to rebuild it. After four nights of supervision, he realized the agent didn't know how to check its results. Once given a specification and a test environment, the rebuild took about two hours. Not every project will move that fast, of course, but the example shows why an agent needs to tell a correct change from an error.

The New Stack reports that autonomous agents wrote the emulator using AWS's public models. Each behavior is checked with a fidelity test, run first against real AWS and then against the emulator. Security agents also review the code during a validation step. In my view, these checks tell us more than the mere fact that an agent wrote the code: they explain how AWS checks the result.

## My take: a testing tool, not a green light

The emulator covers modeled APIs, not the internal services your team has built around them. An application can pass its tests against the emulator and still hit a defect in a homegrown dependency or in a real environment. API fidelity helps, but it doesn't replace testing your own systems or pre-production checks.

It remains to be seen how it will perform in projects that go beyond the supported APIs, and how much confidence teams will place in its results. The fidelity tests AWS describes check behaviors; they don't guarantee that every business scenario is covered.

To me, AWS Emulator is a step in the right direction: the potential gain comes from fast, credible feedback, not simply adding an agent to development. I'd treat it as an additional test environment, with scenarios for important integrations and separate checks for internal services. If you use agents, the key question is whether they can see their mistakes and fix them before deployment.

## Sources

- [Test your applications against AWS locally with AWS Emulator](https://aws.amazon.com/blogs/aws/test-your-applications-against-aws-locally-with-aws-emulator/)
- [AWS Emulator proves agents need a verification loop. Realism is the hard part.](https://thenewstack.io/aws-emulator-verification-loops/)
