AWS Emulator, released by AWS on November 11, 2026, runs the AWS APIs on your machine, with no AWS account needed. It cannot show what only production shows: IAM policies it does not evaluate the way AWS does, separate accounts and Regions, real load, and operations it does not match yet. For those, monitor your AWS calls in production.
Every fact about the emulator below comes from AWS's own docs, blog post and GitHub repository, checked on November 17, 2026, and cited inline. If you want the general version of this problem (data volume, config, concurrency), read why your app works locally but breaks in production. This post is about the AWS part.
What the emulator tests, and what only production shows
AWS is upfront about this. The emulator is "for building and testing", not for production workloads or security testing, and its user guide lists the limits.2 Read them as a list of the failures your green CI run says nothing about.
| What can go wrong | What AWS Emulator does | Where you find out |
|---|---|---|
| Your code sends an invalid request | Returns the same validation error as AWS where the operation is implemented, for example a DynamoDB table name that is too short2 | Locally, in your tests |
| The operation is not implemented | Returns HTTP 501 with the error code NotImplemented, so the test fails right away3 | Locally, in your tests |
| Missing or wrong IAM permissions | Does not evaluate IAM or resource-based policies the way AWS does; a call AWS would deny can succeed1,2 | A real AWS account, or production |
| Cross-account or cross-Region behavior | Accepts any Region and account ID but does not keep resources apart by them2 | A real AWS account, or production |
| A feature missing in your Region | Verified against AWS in us-west-2 only (us-east-1 for global services)2 | Production |
| Behavior under load, or over days | Not tested for long-running use or load testing; keeps everything in memory and deletes it on stop2 | Production |
| Data plane calls and infrastructure as code | Control plane calls match AWS most closely; data plane and CloudFormation, Terraform and CDK support vary by service3 | Check the fidelity scores, then production |
| Real network: latency, timeouts, throttling | Requests go to a local process, not to AWS5 | Production |
From the AWS Emulator user guide and README, November 17, 2026.
The IAM row is the one that bites small teams. The test suite passes, the deploy goes out, and the first real request from the worker is refused with AccessDenied because its role was never given the new permission. Nothing locally could have told you.
What AWS Emulator is
AWS Emulator is a local program that serves an AWS API endpoint. You start it, set environment variables so the AWS CLI or your AWS SDK points at it, and run your code as usual. Requests go to the emulator, not to AWS, so you need no AWS account. There is no graphical interface.5 AWS announced it on November 11, 2026.1
- Cost and license. No additional service fee. The source is on GitHub under CC0, except vendored framework code under Apache 2.0.5
- Where it runs. On Linux from an RPM or Debian package; on macOS and Windows in Docker, from an image you build with AWS's Dockerfile. Tests written in Rust can run it inside the test process (embedded mode).2 By default it listens on 127.0.0.1, port 9297.5
- Set up by your coding agent. AWS ships an
aws-emulatorskill that installs, starts and connects the emulator, and checks whether your project's AWS calls are covered by passing fidelity tests.4,5 - Kept current by agents. AWS says AI agents keep the emulator up to date with AWS, with updates many times a day. The repository does not accept pull requests; you report differences as issues.2,5
- Telemetry. On by default, anonymous usage and error data only. Turn it off with
--telemetry offorEMULATOR_TELEMETRY=off.5
How close is AWS Emulator to real AWS?
AWS measures the gap with fidelity tests: short SDK programs, verified against real AWS, that assert the result, the resulting state and, for invalid calls, the exact error. A service's fidelity score is the number of its tests the emulator passes out of the total. AWS publishes the tests, including the failing ones, and a score with every release.3
We counted the scores file of release v1.0.487, scored on November 17, 2026: 30,887 of 43,548 fidelity tests pass, 12,577 fail and 84 are skipped.6 Counting only the tests that call a single service, S3 passes 1,076 of 1,226, DynamoDB 1,203 of 1,481, SQS 284 of 335, IAM 602 of 692 and Lambda 476 of 788.6 The numbers move every release, and AWS notes that a score can drop when new tests find a gap that was already there.3
Individual gaps live as files in the repository: on November 17 there were about 5,800 under issues/things-that-do-not-work/ and about 15,900 already moved to things-that-now-work/.7 AWS's advice is to list the operations your app calls, check their fidelity tests, and compare against real AWS for anything no test covers.4 Its own blog post goes further: test the whole application on AWS before you go to production.1
AWS Emulator vs LocalStack
LocalStack is the emulator most teams already know, so it is the obvious comparison. The difference that matters for production failures is permissions.
| AWS Emulator | LocalStack | |
|---|---|---|
| Made by | AWS | LocalStack, a third party |
| Price | No additional service fee5 | Hobby free for non-commercial use; Base $39 a month billed yearly, Ultimate $898 |
| Account needed | No AWS account5 | A LocalStack account and auth token8 |
| IAM policy enforcement | Not evaluated the way AWS does2 | Basic from Base, advanced on Ultimate8 |
| Source | Public on GitHub, CC05 | See LocalStack |
| How fidelity is reported | Per-service fidelity scores with every release3 | See LocalStack |
Prices in USD, from each vendor's own page on November 17, 2026.
Either way, an emulator answers "does my code talk to AWS correctly?" It cannot answer "does it work in my account, under my traffic, today?" That second question only has an answer in production.
How to see AWS failures in production
Keep the emulator for fast tests. Then make sure the failures it cannot catch reach you before a customer does. For the general case, see monitoring errors in production; for AWS calls, it comes down to five steps.
- Keep the emulator in CI. Run it for every change, with the skill's check telling you which of your calls it covers well.4
- Run one real test on AWS before release. A short smoke test in a real account catches the IAM and cross-account mistakes the emulator lets through.1
- Record every AWS call as a span. OpenTelemetry has AWS SDK instrumentation for Node.js (in the auto-instrumentations bundle) and for Python through botocore. Each call becomes a span tagged with the service and operation, such as S3 and PutObject.9,10
- Send traces and logs somewhere that groups errors. A failed AWS call should become one issue with a count, not a thousand log lines nobody reads.
- Get told when a new one appears. An alert on a new issue is how the AccessDenied after a deploy reaches you, instead of a support ticket from a customer.
Doing it with Fixter
Fixter (fixter.dev) is ours. Fixter finds and fixes the issues in your app in production, from your coding agent: errors, failing infrastructure, slow requests and downtime. It finds the root cause and fixes it: in your agent over MCP, or as a pull request ready for your review. Nothing to learn, built for small teams.
Your app sends standard OpenTelemetry logs and traces.11 Errors in them become issues on their own, with no extra error SDK.12 When the upload worker starts logging AccessDenied from S3, you hear about it by email or Slack, with the root cause already worked out. To set it up, paste this into your coding agent: Read fixter.dev/llms.txt and set up Fixter. Free plan, paid from €20 a month.13
The emulator makes the local loop fast. Production monitoring covers what happens after the deploy. You need both.
Key takeaways
- AWS Emulator runs the AWS APIs locally, free, with no AWS account, and is set up by a coding agent skill
- It does not evaluate IAM policies, separate accounts or Regions, or claim to handle load; AWS says not to use it for security testing
- On November 17, 2026, 30,887 of its 43,548 fidelity tests passed; check the scores for the services you use
- LocalStack enforces IAM policies on its paid plans; AWS Emulator does not
- Record AWS SDK calls as OpenTelemetry spans so the failures the emulator cannot catch show up as issues in production
Frequently asked questions
What is AWS Emulator?
AWS Emulator is a local program from AWS that serves the AWS APIs on your machine, a development server or in CI. You point the AWS CLI or an AWS SDK at it with environment variables and your code runs unchanged, with no AWS account. AWS made it available on November 11, 2026, and publishes the source on GitHub under CC0.
Is AWS Emulator free?
Yes. AWS says the emulator has no additional service fee and needs no AWS account; you pay only for AWS resources when you deploy on AWS. Telemetry about how you use it is on by default and can be turned off with --telemetry off or EMULATOR_TELEMETRY=off.
AWS Emulator vs LocalStack: which should I use?
AWS Emulator costs nothing, needs no account and is CC0, but it does not evaluate IAM policies the way AWS does. LocalStack needs an account; its free Hobby plan is for non-commercial use only, and IAM policy enforcement starts on the Base plan at $39 a month billed yearly. If you need to test permissions locally, that is the deciding difference.
Can I test IAM permissions with AWS Emulator?
No. AWS's own docs say the emulator does not evaluate IAM policies and resource-based policies the way AWS does, and tell you not to use it to test security. A call that AWS would refuse with AccessDenied can succeed locally, so permission mistakes show up in a real AWS account or in production.
Which AWS services does AWS Emulator support?
It supports the APIs of AWS services that have an API model in AWS's api-models-aws repository. How closely it matches AWS varies by service: control plane calls (create, describe, list, delete) match most closely, while data plane calls and CloudFormation, Terraform and CDK support vary. Unimplemented operations return HTTP 501 NotImplemented.
How do I catch AWS errors in production?
Instrument your app with OpenTelemetry, including its AWS SDK instrumentation, so every AWS call becomes a span with the service and operation name. Send those traces and your logs to a monitoring tool that groups errors into issues and alerts you when a new one appears. Then an AccessDenied or a timeout from S3 or DynamoDB reaches you before a customer reports it.
Sources (13), all checked November 17, 2026
- AWS News Blog, "Test your applications against AWS locally with AWS Emulator" (November 11, 2026)
- AWS Emulator User Guide, What is AWS Emulator (use cases, limitations, features)
- AWS Emulator User Guide, Fidelity in AWS Emulator (fidelity tests and scores)
- AWS Emulator User Guide, Checking whether your project works with AWS Emulator
- AWS, aws-emulator repository README (quick start, telemetry, license, contributing)
- AWS, aws-emulator releases (release v1.0.487 and its scores.json, scored November 17, 2026)
- AWS, aws-emulator issues directory (things-that-do-not-work and things-that-now-work)
- LocalStack pricing (plans, IAM policy enforcement by plan)
- OpenTelemetry, aws-sdk instrumentation for Node.js (span attributes)
- OpenTelemetry, botocore instrumentation for Python
- Fixter docs, Telemetry (standard OpenTelemetry logs and traces)
- Fixter docs, Issues (how errors in logs and traces become issues)
- Fixter pricing