Source: AWS News Blog
AWS has announced AWS Emulator, a local emulator for Amazon Web Services that developers run on their own machine. The AWS Command Line Interface, the AWS SDKs and coding agents such as Kiro or Claude Code talk to it over a local HTTPS endpoint, using the same AWS APIs they would use in the cloud. The announcement was published on 11 November 2026 on the AWS News Blog. AWS Emulator carries no additional service fee, you pay only for AWS resources when you actually deploy on AWS, and its source code is available on GitHub.
How it works
The emulator is implemented in Rust so it stays light on CPU and memory on a laptop. You install it from an RPM or Debian package on Linux, and on macOS and Windows you run it in Docker. On startup it generates its own credentials, a config file and a certificate, and it serves HTTPS on 127.0.0.1:9297 so only your own computer can reach it. Because it is built from the same API models the AWS SDKs use, your requests and the errors you get back have the same shape as on AWS. The generated access key IDs start with EMULATOR so they cannot be mistaken for real AWS keys, every request must be signed with Signature Version 4 just like on AWS, and a single local account with ID 000000000000 keeps test state isolated from production.
Built for tests and coding agents
A unit test that creates an Amazon DynamoDB table, writes an item and reads it back is the same test, and it runs on your machine without a deployment. For test suites there is also an embedded mode, available for the AWS SDK for Rust, which runs inside the test process itself. Each embedded instance keeps its own state, so tests do not share buckets, tables or queues, and you can run many of them in parallel.
AWS says an emulator is only useful if a test that passes against it would also pass against AWS, so the team measures that directly with fidelity tests, short SDK-driven workflows whose expected behaviour is verified against real AWS before the emulator is judged against it.
Why it matters for European DevOps teams
For teams running CI pipelines in Europe, this removes a classic bottleneck: integration tests that depend on live AWS accounts, shared test environments and accidental cloud spend. Local emulation means faster feedback, reproducible runs and fewer credentials in pipeline configuration. It also fits the growing regulatory pressure in Europe to keep tight control over where data and test workloads live, since nothing leaves the machine. The emulator does not replace integration testing against a real account before release, but it moves a large share of everyday verification off the cloud bill.
If you want help designing CI/CD pipelines that test AWS workloads efficiently, or reviewing how your team manages cloud costs and credentials, contact Excello Digital for practical advice from engineers who build and run cloud infrastructure every day.