YuSMP Group logo
YuSMP Group Editorial Team Editorial team, YuSMP Group
A laptop on a dark desk with a small glowing cloud of connected server blocks floating above the keyboard, suggesting a cloud environment running locally

The short version

AWS Emulator gives teams a free local stand-in for more than 200 AWS services, so unit and integration tests can run without an account, a network or a cloud bill. Teams building on AWS get a faster loop for developers and coding agents. Security, IAM and scale still need a real account.

What did AWS release?

AWS Emulator is a local program that answers AWS API calls on your own machine. It listens on a local HTTPS endpoint, by default 127.0.0.1:9297, and generates its own credentials, config file and certificate at startup. Point the CLI or an SDK at it with AWS_ENDPOINT_URL, and scripts that create an SQS queue or write to a DynamoDB table run unchanged.

AWS ships it as RPM and Debian packages for Linux. On macOS and Windows it runs in Docker, and Rust projects can embed it in tests through a separate crate. Each instance keeps its own state in memory, which makes test runs isolated and repeatable. According to The Register, AWS also offers an agent skill so coding agents can use it directly.

How did AI agents build it?

AWS says the emulator was written and is maintained by autonomous agents. “The emulator was written entirely by autonomous agents. Our team hasn’t written or reviewed any of the code,” Matt Goldberg, the AWS senior principal engineer behind the project, wrote in a blog post quoted by GeekWire.

The agents run on Amazon Bedrock AgentCore in three teams:

  1. Test writers turn public AWS API models into “fidelity tests” and check each one against real AWS.
  2. Test runners replay those tests against the emulator and file an issue for every mismatch.
  3. Fixers take one issue per agent run and patch the code.

Every change passes an automated gate where other agents check coding standards and security. AWS publishes fidelity scores per service in a “k of n” format, along with an open evaluation suite and a public list of known gaps. Goldberg wrote that hundreds of agents now fix thousands of issues a day.

Where does AWS Emulator fall short?

AWS is explicit that this is not a full copy of its cloud. The limits matter most for anything security- or scale-related:

AreaWhat the emulator does today
IAMDoes not evaluate IAM or resource-based policies the way AWS does
Accounts and RegionsSingle account; no cross-account or cross-Region behavior
Failure modesNo throttling or outage simulation (IDC analyst Devin Pratt, via InfoWorld)
IsolationDoes not sandbox the code it runs
CoverageOperations without an implementation return HTTP 501
FidelityVaries by service; check the published scores before relying on one

The alternative most teams already know is LocalStack, which this year moved its free version behind an account requirement and limited it to noncommercial use, according to GeekWire. AWS Emulator is free and public domain, but it is new and has a shorter list of features.

What it means for US & EU software teams

Faster, cheaper CI test loops

The clearest win is in CI. Tests that create real resources are slow, cost money and need credentials in the pipeline. A local endpoint removes all three for most API-level tests, and it can replace many hand-written mocks that drift away from real service behavior.

Safer test loops for coding agents

It also changes how teams can let coding agents work. An agent that tests against a local emulator never needs cloud credentials, so a mistake can’t delete a production bucket or run up a bill. For regulated teams in FinTech or HealthTech, keeping test data on the machine also keeps it out of shared cloud accounts.

Where you still need a real AWS account

The limits define where it stops. Because IAM policies are not evaluated, a test that passes locally says nothing about whether a role can actually reach a resource. Keep a short suite of tests against a real sandbox account for permissions, quotas, cross-Region setups and failure handling.

How to treat it in security reviews

One more point for security reviews: AWS says no human wrote or reviewed this code, and the emulator does not sandbox what it runs. Treat it like any third-party dev tool. Pin a version, run it only on developer machines and CI runners, and keep it away from production networks.

How should teams start using it?

  1. Check fidelity first. Look up the published scores for the services your app uses before moving tests over.
  2. Start with one pipeline. Point a single service’s integration tests at the emulator and compare results with your current setup.
  3. Keep a real-account suite. Leave IAM, quota and multi-Region tests on a sandbox AWS account.
  4. Give agents the emulator, not keys. Configure coding agents to test locally by default.
  5. Pin and review. Fix the emulator version in CI and update it on purpose, since the code changes daily.

Frequently asked questions

What is AWS Emulator?

AWS Emulator is a free local program from AWS that serves an AWS API endpoint on your own machine. It is built from more than 400 public AWS API models covering more than 200 services, so the AWS CLI, AWS SDKs and AI coding agents can create and use resources such as SQS queues or DynamoDB tables without an AWS account or a network connection. AWS released it on November 11, 2026.

Is AWS Emulator free, and what is the license?

Yes. AWS charges no service fee for the emulator; you pay only for resources you later deploy to real AWS. The code is released under the CC0 1.0 Universal public domain dedication, with the full commit history on GitHub.

What does AWS Emulator not do?

AWS says it does not evaluate IAM or resource-based policies the way AWS does, runs as a single account and does not reproduce cross-account or cross-Region behavior. An IDC analyst quoted by InfoWorld and GeekWire added that it does not simulate throttling, outages or regional differences in service availability, and it does not sandbox the code it runs. Unsupported operations return HTTP 501.

How do I point my code at AWS Emulator?

Start the emulator and set AWS_ENDPOINT_URL to its local HTTPS endpoint, by default https://127.0.0.1:9297. The emulator generates its own credentials, config file and certificate on startup, and existing CLI scripts and SDK code keep working without changes. Linux users can install RPM or Debian packages; macOS and Windows users run it in Docker.

Is AWS Emulator a replacement for LocalStack?

Not one-for-one yet. Both emulate AWS APIs locally, but AWS Emulator keeps state in memory per instance, supports one account and skips IAM policy evaluation, while LocalStack has a longer track record and paid features. The main draws of AWS Emulator are the price and license: it is free and public domain, while LocalStack this year moved its free tier behind an account and limited it to noncommercial use.

Sources

AWS News Blog — Test your applications against AWS locally with AWS Emulator (primary source, November 11, 2026)
AWS What’s New — AWS Emulator is now available (November 11, 2026)
GeekWire — AWS gives developers a free local stand-in for its cloud, built from scratch by AI agents (November 11, 2026)
The Register — AWS distills its cloud into a local emulator that runs on your PC (November 12, 2026)