April 13, 2026 · v1.2.9 · Contributed by @AdigaAkhil
Starting with v1.2.9, the MiniStack Docker image ships with AWS CLI v1 built in. You no longer need to install it yourself or mount a binary from your host. The image went from 242MB to 269MB — a +27MB trade-off for convenience.
Init scripts also got an upgrade: .py files are now supported alongside .sh scripts. Drop a Python file in ready.d/ and it runs automatically after MiniStack starts.
The biggest quality-of-life improvement: init scripts automatically receive credentials and endpoint configuration. No manual setup needed.
These are set automatically for init scripts — you don't need to configure them:
AWS_ACCESS_KEY_ID=testAWS_SECRET_ACCESS_KEY=testAWS_DEFAULT_REGION=us-east-1 (or your MINISTACK_REGION)AWS_ENDPOINT_URL=http://localhost:4566If you set your own values via docker run -e, those take priority. This also works with multi-tenancy — set AWS_ACCESS_KEY_ID to a 12-digit number and init scripts create resources under that account.
Both MiniStack-native and LocalStack-compatible paths are supported:
/docker-entrypoint-initaws.d/ready.d/*.{sh,py} or /etc/localstack/init/ready.d/*.{sh,py}/docker-entrypoint-initaws.d/*.{sh,py} or /etc/localstack/init/boot.d/*.{sh,py}Scripts from both paths are merged, deduplicated by filename, and run in alphabetical order.
Before: 242MB — After: 269MB (+27MB)
The CLI is AWS CLI v1 installed via pip (Apache 2.0 license, maintained by Amazon). Help examples and Python cache are stripped in a multi-stage build to keep the delta small.
Thanks to @AdigaAkhil for contributing this feature (#272).