The AWS Emulator serves HTTPS on 127.0.0.1:9297, allowing local API calls without contacting the cloud.
*AWS Emulator lets developers test code against a local copy of AWS APIs without an AWS account or extra fees. It runs as a CLI or Docker container and integrates with AI coding agents. The tool is open‑source, but Amazon warns against production or security use.*
Amazon has open‑sourced a full‑stack emulator of its cloud APIs, positioning it as a development‑only tool. The project lives on GitHub under aws/aws-emulator and already records 29,684 commits, reflecting a broad service coverage. By routing calls to a local HTTPS endpoint, the emulator lets engineers run code that would normally hit AWS without an account or incurring fees. The design supports both server mode—where the CLI or SDK points to the emulator—and embedded mode, where Rust tests link directly to the emulator’s HTTP client. Amazon also bundles an AI coding agent skill that can spin up the emulator automatically, further lowering the barrier for rapid prototyping.
AWS Emulator is a local program that mimics the AWS API surface. After launching, it listens on 127.0.0.1:9297 with a self‑signed HTTPS certificate. Developers point the AWS CLI, SDK, or an AI coding agent at the emulator by setting environment variables or passing the emulator’s HTTP client directly in embedded mode. The emulator serves in‑process Rust crates for each AWS service, allowing tests to run without contacting the real cloud. It is hosted on GitHub under the aws/aws-emulator repository, which tracks 29,684 commits across service crates.
The emulator eliminates the need for an AWS account during development and continuous integration. It incurs no additional service fee; costs arise only when code is deployed to actual AWS. Teams can run the emulator on a developer workstation, a CI server, or inside a Docker container on Windows or macOS. The tool integrates with AI coding agents that can install the aws-emulator skill and configure the environment automatically, streamlining setup for rapid prototyping.
Amazon explicitly advises against using the emulator for production workloads or security testing. Gaps in service fidelity are tracked in the repository’s issues directory, with separate folders for non‑working and now‑working APIs. Fidelity scores are published with each release. Because the emulator runs locally, it cannot replicate the full security posture of the live AWS environment, and any security‑related bugs would not be exposed.
Building from source requires a Rust toolchain, Cargo, a C compiler, and at least 100 GB of free disk for the target directory. A cold full build compiles every service crate and can take several minutes on a multi‑core machine. Most users install pre‑built RPM or Debian packages on Linux, or run the Dockerfile on Windows/macOS. Embedded mode compiles the emulator into the test binary, so caching the Cargo target directory or using sccache in CI is recommended to speed up incremental builds.
On Windows (and macOS) you run the emulator in a container built from a short Dockerfile, as described in the Getting started with Docker guide.
No. The emulator runs locally and does not require an AWS account; requests go to the emulator, not to AWS.
No. Amazon advises against using the emulator for production workloads or to test security.
The AWS Emulator fills a niche for fast, cost‑free cloud API testing, yet its explicit security disclaimer and fidelity gaps keep it firmly in the dev‑only arena. As AI agents automate more of the setup, adoption will likely rise, but enterprises must still rely on real AWS environments for any production or security‑critical workloads.
Sources: Hacker News, https://www.aboutamazon.com/news/aws/how-autonomous-ai-agents-built-aws-emulator, https://www.allthingsdistributed.com/2026/11/aws-emulator-and-the-engineers-job-when-agents-write-the-code.html, GitHub - aws/aws-emulator