· ai-devtools
AWS releases free local Emulator, built by agents, supporting 200+ services
The sheer volume of commits, numbering 29,684 in a repository less than a month old, has sparked considerable debate among developers regarding the trustworthiness of the new AWS Emulator.
This free, CC0-licensed local stand-in for over 200 of AWS's services was developed entirely by autonomous AI agents, according to AWS. The tool, which ships as a single Rust binary derived from AWS's 438 public API models and listens on port 9297, aims specifically to support the testing routines of coding agents.
Following the launch on November 20, 2026, the community has offered a mixed reception to this novel development. Daniel Abib, in a launch post, noted that setting up the emulator requires only modifying environment variables for existing SDKs, CLIs, or coding agents, stating that "your existing tests, CLI scripts, and coding agents keep working the way they already do." This setup involves setting variables such as `AWS_ENDPOINT_URL=https://127.0.0.1:9297` and specifying credential paths.
In a demonstration shared in the same post, Kiro was tasked with creating and subsequently retrieving a DynamoDB table, executing standard CLI commands against the local endpoint. The commands shown included creating the table "kiro-demo" with a string key "id," inserting an item, and then fetching that item back.
Matt Wood, AWS's chief AI and technology officer, emphasized the critical nature of this simulation loop, warning, "A coding agent can build a lot of software around an incorrect assumption." He further clarified the potential danger, explaining that an agent learns from its operational environment; if the emulator permits behavior that AWS rejects, training could inadvertently solidify an error, and an agent might exploit a flaw unique to the emulator. To address this, fidelity scores are published with every release, detailing how many tests passed out of those verified against actual AWS, and these failing tests are made public, prompting Abib to advise readers to "read a score as a snapshot of a product that's improving."
Matthew Goldberg, a senior principal engineer, credited the project's genesis to a simple, three-line directive given to Kiro: "the simplest prompt that I could think of without any expectation that this would work": Write tests based on the AWS Command Line Interface (CLI), Iterate on those tests until they pass against real AWS, and Build an in-memory implementation that those same tests pass against. Kiro delivered a functional first version of Amazon Simple Queue Service (Amazon SQS) after fifteen minutes, leading Goldberg to refine his prompt and have Kiro develop the remainder of AWS over the weekend. Although initial versions possessed gaps, the tool proved compelling enough that his team began using it for software testing that very Monday.
The production version is managed by three distinct agent teams: one team oversees the test suite, another hunts for emulator defects, and a third works to resolve those issues. Goldberg elaborated that every correction must pass a rigorous gate, which includes compiling the change and subjecting it to agent reviews for security, coding standards, and fidelity regression. He asserted, "Our team hasn't written or reviewed any of the code," detailing that if any of these checks fail, the change returns to the agent for revision; otherwise, it merges into the mainline. He noted, "We've seen thousands of issues fixed every day as hundreds of agents concurrently work on the codebase. Without this merge gate, we wouldn't trust what our agents are building."
Swami Sivasubramanian recounted a personal experience where Kiro helped rebuild a replication engine that would have taken his team four months manually. He noted that after supervising the agent for four nights, he recognized the lack of a result-checking mechanism; however, once a specification and a testing environment were in place, the rebuild took merely about two hours. In his experience, the engineer's function shifts to "to build the specs, tests, and merge gates that decide when that work is correct."
Independent measurements from Kento Ikeda, an AWS Community Builder, who tested version 1.0.322 in GitHub Actions the day after the debut, revealed varied results. DynamoDB, S3, and SQS achieved fidelity rates of approximately 60 to 70 percent at the service level, while the operations code they called registered between 80 and 100 percent, whereas CloudFormation scored near 20 percent. Ikeda observed that while the emulator mirrored AWS's error messaging, a new DynamoDB table remained in a CREATING state for three seconds before rejecting writes. He concluded that "Being generated from API models only means the shape of requests and responses matches AWS," positioning the tool as a middle layer between mocks and a live sandbox, rather than a complete substitute for either.
The launch announcement strongly cautioned against using the emulator for security validation, stating explicitly: "Don't use the emulator to test whether your application is secure." This is because it does not assess AWS Identity and Access Management (IAM) policies or resource-based policies as AWS does, meaning a request denied by AWS could succeed within the emulator. Users are urged to keep live credentials out of test environments and to validate security and the entire application on AWS prior to going live. Furthermore, the emulator does not simulate throttling, regional variations, or outages; unimplemented operations return an HTTP 501, and telemetry is active by default. The repository is also not accepting pull requests.
The discussion on Hacker News highlighted the security omission; one user quoted the security page's statement that the emulator "never denies a request signed with its own key" and questioned the exclusion of IAM, suggesting it might be because the agents were limited to the public API surface, though others speculated it could prevent trivial use of `aws-emulator` as AWSaaS. Regarding the product's longevity, the initial query about whether it was "just an exercise or a real product they are going to ship and maintain" was answered by an AWS staff member stating, "It's a real product that we plan to maintain." Another commenter expressed skepticism, remarking that the repository "does not instill confidence" given its rapid development. On r/aws, the most highly-voted comment inverted Amazon's stance, labeling the use of agents to fix code "without human review" as a poor practice for pre-production testing. The counterargument was that since API specifications and SDKs already exist, a server built upon a fixed contract is an appropriate place for agents to iterate until tests pass. The timing of this release is significant, especially considering that LocalStack's free Hobby plan now requires an account and bans commercial use, with paid tiers starting at $39 monthly, prompting some developers to migrate to Floci. One developer contextualized the AWS release against this backdrop, noting that the ecosystem was already filled with "slopware and low trust" following LocalStack's changes, adding, "I don't think this is worse, for now at least," because AWS's offering is free and open to forking. Sivasubramanian mentioned that AWS intends to provide further details about this work at re:Invent in December.
Why it matters
This tool provides developers with a local testing environment for AWS services, allowing coding agents to iterate faster without relying solely on live cloud infrastructure. Practitioners should note that the emulator is not a replacement for real AWS, as fidelity scores reveal gaps between the emulation and actual service behavior.





