AWS launches a local emulator for its cloud APIs

AWS has made available a local emulator of its APIs, usable without an AWS account. The tool targets developers and coding agents, with a logic of faithful tests but no value for validating production security.

AWS has released AWS Emulator, a local emulator of its APIs available since November 11, 2026, designed to work without an AWS account. The tool covers 438 AWS API models and more than 200 services, allowing developers and coding agents to test code on their machine before any deployment. The idea is simple: run the same calls as in the cloud but without waiting for an AWS region or paying for infrastructure still in the trial phase.

A cloud that fits on the desktop, but with safeguards

The emulator connects via a local HTTPS entry point, while the AWS SDK, CLI, and code agents continue to call the same APIs as in production. Environment variables redirect these tools to the user's machine without modifying the application code. AWS offers RPM and Debian packages for Linux, a Docker image for macOS and Windows, as well as an embedded mode for Rust testing.

In this context, the tool mainly targets the write-test-fix cycle. An agent can create a resource, check the result, then adjust its code without waiting for a real deployment. AWS also cites development servers and continuous integration among compatible environments. The emulation side remains free, even if resources deployed in the AWS cloud are still billed.

When agents write code, humans write the rules

Matthew Goldberg, senior principal engineer at AWS, explains that his team neither wrote nor directly reviewed the emulator code. Humans rather built the framework around the project: specifications, test machinery, merge gates, and release pipeline. The starting point was an Amazon SQS emulator prototype generated by the coding agent Kiro in about fifteen minutes, based on instructions to write tests, validate them on real AWS, and build an in-memory implementation.

Then, AWS structured the work into three bounded agent teams: test writers, problem detectors, and correcting agents. According to Goldberg, the company now talks about tens of thousands of fidelity tests, with thousands of fixes applied daily by hundreds of agents working in parallel. Not bad for a factory where the foreman doesn’t drink coffee.

Fidelity as a metric, not security

A fidelity test is a short scenario compared to real AWS. To succeed, the emulator must return the correct response to each call, including HTTP code, response body, and exact error message, while creating the expected resources. Unimplemented operations return HTTP 501, making discrepancies immediately visible. Each version also publishes scores by service, and AWS warns that adding new tests can lower a score even if the tool progresses.

This precision has a clear limit: AWS Emulator is not a security testing environment. It does not reproduce IAM management or resource-based policies as AWS would, meaning a request denied in the cloud may pass locally. The intended use remains development and functional testing, not production load validation. Each instance is designed for a single account and region, keeps resources in memory, and erases them on shutdown.

What this launch says about software work at AWS

Swaminathan Sivasubramanian summarizes the role change: the engineer decides what to build and defines specifications, tests, and merge safeguards, while agents produce and verify code. AWS illustrates this shift with an example from Alf, its former distributed locking service. The first rewrite supervised by Kiro took four nights due to lack of a simple way to validate results; with a specification and test environment, the rebuild dropped to about two hours.

The launch of AWS Emulator formalizes this method in a publicly distributed product, with code published under CC0, except third-party components under Apache 2.0. The GitHub repository exposes the commit history and folders separating resolved and unresolved fidelity issues but does not accept pull requests. Users can, however, report bugs and behavior discrepancies via GitHub Issues. The tool's practical scope will therefore depend on the expanding public test and remaining gaps between local emulation and real AWS.

By the numbers

  • 438 API models — base covered by AWS Emulator, according to AWS.
  • More than 200 services — scope announced at launch on November 11, 2026.
  • HTTP 501 — response returned for an unimplemented operation.
  • Two hours — time mentioned for assisted reconstruction after specification and tests.
  • Four nights — duration of the first supervised trial on Alf, according to Swaminathan Sivasubramanian.

To read