+362
Daily
8,572
stars
369
forks
20
watchers
0
prs
463
issues
30
releases
README
AWS Emulator README AWS Emulator is a local emulator of the AWS APIs. You use it to test your software without calling AWS, on your own machine, on a development server, or in continuous integration (CI). You don’t need an AWS account. Your requests go to the emulator, not to AWS. So you work with emulated resources instead of AWS resources. AWS Emulator has no additional service fee. You pay only for AWS resources when you deploy on AWS. The emulator is a local program that serves an AWS API endpoint. It has no graphical interface. After you start the emulator, you set environment variables to point the AWS CLI or an AWS SDK at its endpoint. Then you run your code as usual. In embedded mode, you pass the emulator’s HTTP client to your SDK instead. AWS Emulator is for building and testing. Don’t use it for production workloads or to test security. See Security in AWS Emulator. Documentation: AWS Emulator User Guide Quick start With an AI coding agent Install the aws-emulator skill, then ask your agent to set up the emulator. This needs the AWS CLI version 2.35.0 or later. See Getting started with an AI coding agent. bash aws agent-toolkit add-skill --skill-name aws-emulator --region us-east-1 Server mode (CLI and any SDK) - Linux: install the RPM or Debian package and run aws-emulator. See Getting started on Linux. - Windows / macOS: run the emulator in a container built from a short Dockerfile. See Getting started with Docker. Point your SDK at a running emulator by setting environment variables. See Pointing your AWS SDK at AWS Emulator. Embedded mode (Rust tests) Add the emulator as a dev-dependency and run it in-process, one isolated instance per test. There is no endpoint URL, certificate, or environment variable to set. Your test wires the emulator's HTTP client straight into the SDK client. See Getting started with embedded mode, and Building from source below for its build cost. Known issues To see how closely each service matches AWS, check the fidelity scores published with each release on the releases page. To check whether your own project is expected to work, see Checking whether your project works with AWS Emulator. Individual gaps are tracked in the repository's issues/ directory. APIs and behaviors that don't work yet are under issues/things-that-do-not-work/, and ones that have since been fixed move to issues/things-that-now-work/. Building from source You need this if you are modifying the emulator, running it from a checkout, or using embedded mode. Embedded mode compiles the emulator into your test binary, so the prerequisites and build-cost guidance below apply to it too. Most other users install a prebuilt package instead (see Quick start). Building from source is supported on Linux (x86_64 and aarch64); on Windows and macOS, use the Docker path above. Prerequisites - A Rust toolchain with Cargo (install via rustup). - A C compiler, such as GCC or clang. Some dependencies build C code. - At least
Top issues
#46EC2 RevokeSecurityGroupEgress: an all-protocols rule named with FromPort/ToPort 0 does not match the default egress rule, so every Terraform aws_security_group fails8 comments · 2026-11-12#33CloudFormation: 51,200-byte template limit is applied to templates referenced by S3 URL (CreateStack and CreateChangeSet)5 comments · 2026-11-12#369S3 PutBucketNotificationConfiguration to SQS fails with "Unable to validate the following destination configurations" when the queue policy has a Deny statement4 comments · 2026-11-13#20Add persistence to maintain data across restarts4 comments · 2026-11-11#421s3: CreateBucket with a public canned ACL succeeds and drops the grant instead of failing with InvalidBucketAclWithBlockPublicAccessError3 comments · 2026-11-14#341EC2: DeleteNetworkInterfacePermission returns 501 NotImplemented3 comments · 2026-11-12#28Lambda nodejs24.x: node:module, node:http, node:https, node:zlib, node:async_hooks, fetch and structuredClone are missing3 comments · 2026-11-12#26S3 refuses every cross-origin browser request (403 "Requests a browser sends from another site are refused") and answers CORS preflight with 501, so bucket CORS rules can't be used3 comments · 2026-11-12
Latest release
v1.0.385 v1.0.385 2026-11-14- fix: sns-8-net-new-validation-causes-string-array - fix: ssm-getopssummary-stub - fix: mediapackage-hls-ingest-endpoint-unauthenticated-put-returns-no - fix: bedrock-agentcore-control-putresourcepolicy-s-resourcenotfoundex... - fix: ds-ec2-2-net-new-causes-a-managed - fix: devops-agent-createasset-mints-asset-assetid-from-a - fix: cloudfront-three-refusal-divergences-oversized-tenant-invalidati... - fix: sts-assumerolewithsaml-refusal-messages-4-net-new-causes - fix: cloudwatch-lambda-logs-2-net-new-causes-cloudwatch - fix: location-getmapsprites-stub - fix: cloudfront-6-net-new-resource-pol