AWS released the AWS Emulator on November 11. It lets the AWS CLI, SDKs, and coding agents send familiar AWS API calls to a local HTTPS endpoint. Linux packages are available, and AWS documents a Docker setup for macOS and Windows. The source code is public.
The emulator generates its own credentials and certificate. A developer can point an AWS client at the local endpoint and exercise API calls without provisioning the corresponding cloud resources. AWS says agents built the implementation, with changes passing fidelity tests before the company publishes them. That describes how AWS produced the emulator. Your application still needs tests for the particular operations it uses.
Split one DynamoDB test into two
Suppose a coding agent adds a worker that writes an order to DynamoDB and reads it back. Give it a local test with two assertions. A valid order should round-trip with the same fields. A deliberately invalid item should lead to the error handling the application expects. Run both with emulator credentials, and have the test runner check the configured endpoint before it starts.
Run a second test in a disposable AWS account. Use the role that the worker will actually assume. Give it access to the test table and deny access to a second table. Success means the first write works and the second attempt is denied. That checks the deployed permission boundary, including the policies and resources the cloud environment actually uses.
The two runs answer different questions. The local loop checks what the code sends and how it handles replies. The cloud loop checks what the deployed identity can do. The proposed checks use the emulator’s documented interface and DynamoDB example. We did not execute them against either environment.
Abdessalam Alaoui
I'm Abdessalam Alaoui, founder of Musthave.AI. I write practical guides to AI models, tools, generative media.
