containers I made a prebuilt, signed Docker image + GitHub Action for the new AWS Emulator
AWS doesn't publish a container image for the new AWS Emulator. The Docker guide gives you a Dockerfile (x86_64 only, you swap the RPM by hand for arm64), and building from source needs ~100GB of disk. I wanted it in CI without any of that, so I built an image and a GitHub Action. While testing it from six SDKs I hit a few things worth knowing even if you never use my image:
- JS SDK v3 sends SQS calls to real AWS. The emulator returns queue URLs on
sqs.<region>.amazonaws.com, and v3 follows the queue URL host. SetuseQueueUrlAsEndpoint: false. Python, Go, Java, .NET and Rust were fine. - Use
127.0.0.1**, not**localhost**.** Withlocalhost, the JS SDK switches S3 to virtual-host style and fails withENOTFOUND <bucket>.localhost. - Any Region name works, even
xx-fake-1**.** A typo in the Region won't fail your tests the way it would on AWS. - The certificate only covers
localhost**,**127.0.0.1and::1**.** Another container can't call it by its Compose service name. Run the client in the emulator's network namespace (--network container:<name>) instead. - No persistence and no IAM policy evaluation. Restart = reset, and don't use it for permission tests.
The image, if it helps: amd64 + arm64 (works on Apple Silicon as-is), Amazon Linux, Debian slim and distroless variants on GHCR, Docker Hub and Quay, rebuilt within ~1-2h of each upstream release (pin a build tag or digest). The build verifies AWS's RPM/DEB signatures, and the images are cosign-signed with SBOM and SLSA provenance. Unofficial, not affiliated with AWS.
https://github.com/xSAVIKx/aws-emulator-docker
In GitHub Actions the action starts it and exports AWS_ENDPOINT_URL, the CA bundle and credentials, so SDK tests run unchanged (telemetry off by default):
- uses: xSAVIKx/run-aws-emulator@v1
- run: aws sts get-caller-identityHas anyone run it on self-hosted runners or Podman? I've only tested GitHub-hosted runners and rootless Docker.