Oleksandr Kuzmenko, EditorPublished 6 min readAI-assisted · editor-reviewed
TL;DR
- AWS Emulator runs over 200 AWS services locally and offline for free.
- The codebase was entirely generated and verified by AI agents against real AWS endpoints.
- Enables zero-latency, zero-cost inner loops for coding agents interacting with cloud primitives.
Key facts
- Supported Services
- 200+ AWS services
- API Models Implemented
- 400+ Smithy models
- Pricing
- Free and offline
- Prototype Build Time
- 15 minutes for SQS prototype
Agent-Authored Infrastructure Emulation
AWS Emulator runs locally and offline on your machine without charges or credentials. Conceived by Matt Goldberg on the AWS Developer Tools team, the system was built on the premise that an agent can build a working service if given formal specifications and access to production for verification. The specifications were provided by Smithy public API models, while live AWS services served as ground-truth truth stores.
Key system properties include:
- Full Agent Authorship: All emulator code was written, tested, and maintained by autonomous agents utilizing Kiro, producing initial service prototypes like SQS in approximately 15 minutes.
- Coverage: Implements over 400 API models across more than 200 AWS services.
- Automated Verification: Changes pass through automated merge gates featuring adversarial security agent evaluations.
The Shift in Engineering Roles
As Swami Sivasubramanian details, when autonomous agents execute code-run-verify loops, the engineer's primary duty pivots from writing implementations to defining formal specifications, integration constraints, and validation gates. Placing faithful emulation directly in an agent's inner loop allows models to achieve correct implementations on the first run without racking up cloud bills.
When to use
- Use inside coding agent loops to give tools immediate offline feedback on AWS API calls.
- Use in local development environments to eliminate AWS sandbox account costs.
When NOT to use
- Do not rely solely on the emulator for complex multi-region replication architectures requiring distributed clock synchronization.
- Do not bypass final end-to-end integration testing against real AWS before production deployment.
What to do today
- Inspect the AWS Emulator release to replace live dev AWS accounts in your local agent testing loops.
- Point local AWS SDK configurations to local emulator endpoints for offline agent tool execution.
Step names are taken from What to do today.
Step names are taken from What to do today. Inspect the AWS Emulator release to replace live dev AWS accounts in your local agent testing loops.. Point local AWS SDK configurations to local emulator endpoints for offline agent tool execution.
- Inspect the AWS Emulator release to replace live dev AWS accounts in your local agent testing loops.
- Point local AWS SDK configurations to local emulator endpoints for offline agent tool execution.
What the community says
The entire AWS emulator was written by agents and will be maintained by agents.
the “agents build it and verify against the real service” approach seems like the actual new thing here.
