Checking whether your project works with AWS Emulator
You can check which parts of your project you can rely on AWS Emulator for. The easiest way is the aws-emulator skill for AI coding agents. With the skill, your agent finds the AWS operations and resources that your project depends on. It checks them against the fidelity tests and fidelity scores for the emulator. It then tells you which parts of your project you can rely on the emulator for, and which ones might behave differently from AWS. If you find a behavior that differs from AWS, your agent can also draft an issue for you. It shows you the draft before it posts anything, so you can review it first.
To install the skill, see To install the skill. Then ask your agent, for example, "Will my app in this repo work on AWS Emulator?"
The fidelity tests don’t cover every behavior yet. We’re continuously adding new fidelity tests based on customer feedback and fidelity issues that we discover. If no fidelity test covers a behavior, the emulator might already handle it correctly, but no fidelity test confirms it yet. For more information about fidelity tests and fidelity scores, see Fidelity in AWS Emulator. To check a workflow yourself, without the skill, do the following:
-
List the AWS operations that your workflow calls.
-
Find the fidelity tests for those operations in the manifest file,
manifest.jsonl, in the aws-emulator-evaluation-suite repository on GitHub. -
Check the fidelity scores for those services on the releases page, for the release that you use. Each score shows how many of the service’s fidelity tests pass.
-
For operations that no fidelity test covers, run your own tests against the emulator and against AWS, and compare the results.
If something acts differently from AWS, tell us. Your reports help us add fidelity tests that cover your scenario. For more information, see Telling us about a difference.