In short: AWS Emulator is a free, open-source program from AWS that answers AWS API calls on your own machine, so your code and your coding agent can create S3 buckets, DynamoDB tables and SQS queues without touching a real account or bill. I installed release 1.0.322 on an Ubuntu box, pointed an unchanged boto3 script at it with the environment variables from the official guide, and it worked on the first try. The catch is fidelity: by my own count of the published test scores, only about 56% of its fidelity checks pass overall, so treat it as a fast test bed, not a copy of AWS.
What AWS Emulator is (and what it is not)
AWS released the emulator on GitHub as aws/aws-emulator, licensed CC0 1.0 (the vendored framework code is Apache 2.0). It is a single local process with no graphical interface. It serves one HTTPS endpoint, https://127.0.0.1:9297 by default, and every supported service is mounted on that one endpoint. The AWS CLI and the AWS SDKs reach it through standard environment variables, so your application code does not change. There is no service fee; you only pay when you later deploy to real AWS.
The launch essay on Werner Vogels' blog frames it as a test environment for the era when agents write much of the code: an agent can run the same create, read and fail loops it would run against AWS, but locally and in seconds. The official guide lists three use cases: local testing, CI pipelines with no AWS account or resources, and prototyping with AI coding agents.
What it is not: a production runtime, a security test tool, or a multi-region simulation. The guide is explicit that it does not evaluate IAM and resource policies the way AWS does, keeps everything in memory (all resources vanish when it stops), does not separate resources by account or region, and is verified against AWS only in us-west-2 (us-east-1 for global services).
Step 1: Install it
Linux (native package)
AWS publishes RPM and Debian packages for x86_64 and arm64. On Debian or Ubuntu, the guide downloads aws-emulator_amd64.deb from downloads.aws.com and installs it with sudo apt-get install -y ./aws-emulator.deb; on Fedora or Amazon Linux 2023 it is a one-line sudo dnf install of the RPM URL. The package puts the program in /opt/aws-emulator/ and the aws-emulator command in /usr/bin/.
Worth doing first: each package has a .sig file next to it. I imported the AWS publishing key, checked its fingerprint (98BC F336 A3BE 53B7 34E9 67C5 2E5B F49B D940 F624, matching the guide) and ran gpg --verify, which reported a good signature made on Nov 11, 2026. The package itself is about 171 MB and unpacks to a single binary of roughly 970 MB, so plan disk space accordingly. Then aws-emulator -v printed version 1.0.322, release date 2026.11.10.
macOS and Windows (Docker)
There is no prebuilt image. The guide gives a short Dockerfile based on amazonlinux:2023-minimal that installs the RPM and starts the emulator with -b 0.0.0.0 inside the container. Two details from the guide matter: publish the port as -p 127.0.0.1:9297:9297 (the short form -p 9297:9297 exposes it to your whole network), and mount ~/.aws/emulator so your SDK can read the certificate and config the container writes. The sample command also caps memory at 2 GiB; if the container goes over, it exits with code 137 and the emulated resources are lost.
With a coding agent
If you work in an agent, the README offers an aws-emulator skill, installed with aws agent-toolkit add-skill --skill-name aws-emulator --region us-east-1 (AWS CLI 2.35.0 or later). The skill installs, starts and connects the emulator and can check which parts of your project it is expected to handle. I did not test the skill path in this run; my test below used the plain server mode.
Step 2: Start it and point your SDK at it
Run aws-emulator and leave that terminal open. I started it with --telemetry off (usage telemetry is on by default; you can also set EMULATOR_TELEMETRY=off or add [telemetry] enabled = false to ~/.aws/emulator/config.toml) and --idle-timeout 900 so it would shut itself down after 15 idle minutes. On startup it wrote four files to ~/.aws/emulator/9297/: ca.pem, config, emulator_credentials and truststore.p12. Those local keys are generated fresh for each run and work only with that run of the emulator.
In a second shell, set the variables from the official guide:
export AWS_ENDPOINT_URL=https://127.0.0.1:9297 export AWS_SHARED_CREDENTIALS_FILE=~/.aws/emulator/9297/emulator_credentials export AWS_CONFIG_FILE=~/.aws/emulator/9297/config export AWS_CA_BUNDLE=~/.aws/emulator/9297/ca.pem export AWS_EC2_METADATA_DISABLED=true export AWS_DISABLE_HOST_PREFIX_INJECTION=true export AWS_REGION=us-east-1 export AWS_DEFAULT_REGION=us-east-1
The guide also says to clear any other AWS credential environment variables in that shell, because they take precedence over the credentials file. Then check readiness with curl --cacert ~/.aws/emulator/9297/ca.pem https://127.0.0.1:9297/__admin/health, which returned ok for me. The quickest sanity check is sts get-caller-identity: on the emulator the account is always 000000000000 and the ARN is arn:aws:iam::000000000000:user/emulator. If you see any other account number, your calls are not going to the emulator.
Step 3: Run real code against it
I used boto3 1.44.1 and a short script with no endpoint or key in the code. Results from that run:
- STS: returned account 000000000000, as documented.
- S3: created a bucket, uploaded a small text object and read it back intact.
- DynamoDB: creating a table named
abfailed with the sameValidationExceptionwording AWS uses for names shorter than 3 characters; a valid table accepted aput_itemand returned it withget_item. - SQS: created a queue, sent and received a message. The returned queue URL still reads
sqs.us-east-1.amazonaws.com/000000000000/jobs, but boto3 kept sending the calls to the local endpoint, so do not panic when you see an AWS hostname in the output. - Virtual-hosted S3: forcing a client to
localhostwith virtual-host addressing sent the request tolm24-demo-bucket2.localhostand failed with an SSL error, exactly the case the guide warns about.
One honest oddity: in my very first pass, a put_item issued immediately after create_table returned ResourceNotFoundException. On the second pass the table was already ACTIVE and the waiter returned at once. Real DynamoDB also requires an active table, so add ddb.get_waiter("table_exists").wait(...) after creating tables in tests anyway; it costs nothing here and keeps the same test valid against AWS.
Step 4: Check fidelity before you trust a green test
Every release ships a scores.json.gz on the GitHub releases page. I downloaded the one for 1.0.322 (scored Nov 11, 2026 UTC) and tallied it myself, counting each test unit toward every service it lists. That is my own arithmetic, not an official per-service score, but it gives a realistic picture:
- Overall: 42,937 units, 24,243 passing (56.5%), 18,614 failing, 80 skipped.
- Stronger: EventBridge 71.5%, Step Functions 70.0%, SNS 69.3%, DynamoDB 68.1%, Secrets Manager 68.0%, SQS 67.8%, S3 62.7%.
- Weaker: CloudWatch Logs 57.3%, EC2 38.8%, Systems Manager 23.8%, CloudFormation 18.9%.
The release notes are long lists of fixes, and the guide says AI agents update the emulator many times a day, so these numbers will move. The official way to check your own project is to list the operations it calls, look them up in the manifest.jsonl of the aws-emulator-evaluation-suite repository, and compare with the scores for the release you run, or ask the agent skill to do it.
AWS Emulator vs LocalStack vs Moto
| Tool | Price | How you run it | Coverage and limits (from official pages) |
|---|---|---|---|
| AWS Emulator 1.0.322 | No service fee; CC0 1.0 license | Linux deb/rpm, Docker image you build, or embedded in Rust tests | One endpoint for all services; in-memory only; no IAM policy evaluation; telemetry on by default; per-release fidelity scores |
| LocalStack for AWS | Hobby free (non-commercial); Base $39 and Ultimate $89 per license per month, billed annually; Enterprise custom | Local emulator; running tests in CI is included from the free Hobby plan | 30+ services on Hobby, 55+ on Base, 110+ on Ultimate; state persistence and basic IAM enforcement from Base |
| Moto 5.2.5 | Free; Apache 2.0 | Python library (@mock_aws decorator or context manager) or moto_server standalone |
Best fit for Python unit tests; install per service with pip install 'moto[s3,...]' or moto[all] |
Editor's note
Good for: integration tests that call several AWS services, CI jobs that should never create real resources, and agent loops that need quick, disposable infrastructure. Restarting the process gives you a clean state for free.
Not for: testing IAM or bucket policies, multi-region behavior, load tests, long-running dev environments, or anything you would call production.
Gotchas I hit or verified:
- InvalidClientTokenId: a leftover access key variable in the shell overrides the emulator's credentials file. With a fake key set, my STS call failed with exactly this error; clearing the variable fixed it.
- SSL errors on S3: keep
127.0.0.1inAWS_ENDPOINT_URL. Withlocalhost, some SDKs (JavaScript, Java, Go by default) put the bucket in the hostname, and the emulator rejects that. - "Could not connect to data-127.0.0.1": host-prefix injection; set
AWS_DISABLE_HOST_PREFIX_INJECTION=trueonly in the emulator shell, because the guide notes it breaks those operations on real AWS. - Emulator gone after the terminal closes: it runs in the foreground; in my first attempt a backgrounded process ended with its shell. Use a dedicated terminal, a service manager, or Docker.
- Port 9297 in use: start with
-p 9300(or-p 0outside containers) and change the port in every variable. - Big build for embedded mode: building from source needs at least 100 GB free for
target/, per the README.
FAQ
Does AWS Emulator cost anything?
No. The README and guide say it has no additional service fee; you pay only for AWS resources once you deploy to AWS.
Can I use it with JavaScript, Java or Go, not just Python?
Yes. It works with the AWS CLI and the AWS SDKs through the same endpoint variable. Some SDKs need an extra setting to trust the emulator's certificate or to disable host prefixes; the "Pointing your AWS SDK" page has a per-SDK table.
Does it keep my data between runs?
No. Everything lives in memory and is deleted when the process stops, along with the files in ~/.aws/emulator/<port>/. That is a feature for tests: each start is a clean slate.
Related on lightmind24: Agent Skills: One SKILL.md for Claude Code, Cursor, Copilot · Claude Code Errors Fixed: Login, PATH, 429 and Usage Limits · Promptfoo Tutorial: Test Your LLM Prompts Before You Ship
Start the emulator, run your test suite once against it, then check the fidelity scores for the services your code depends on before you trust the green checkmarks.
Screenshots: see the official GitHub README and AWS documentation screenshots, plus my own terminal captures from this test run, at the end of this post. Images: GitHub (aws/aws-emulator), AWS documentation, and lightmind24 own test run.
Last verified: 2026-11-12
Sources: aws/aws-emulator README · AWS Emulator releases (v1.0.322, scores.json.gz) · What is AWS Emulator? · Getting started on Linux · Getting started with Docker · Pointing your AWS SDK at AWS Emulator · Checking whether your project works · All Things Distributed launch essay · LocalStack pricing · Moto getting started
lightmind24 is an independent review site, not affiliated with Amazon Web Services, LocalStack or Moto.
댓글
댓글 쓰기