Goku (formerly Mimir): local AWS cloud in one image. 73 services, 60 consoles, real runtimes.
3.2K
See your cloud, before you ship your cloud.
Mimir is now Goku. It's the same product with a new name, as of 4.0. The image name, your container and your saved data all stay the same, and
MIMIR_*settings still work.
Goku is a local AWS cloud for building, testing and learning cloud infrastructure on your machine. You don't need an AWS account, you don't pay an AWS bill, and you don't need cloud credentials.
macOS / Linux:
curl -fsSL https://tanuj24.github.io/mimir/install.sh | sh
goku start
Windows (PowerShell):
irm https://tanuj24.github.io/mimir/install.ps1 | iex
goku start
goku start pulls this image, starts it and opens the console. Point your AWS CLI and SDKs at it with eval "$(goku env)" (or goku env --shell powershell | Invoke-Expression on Windows). The former mimir command still works as a deprecated alias.
docker run -d --name mimir \
-p 8080:80 -p 4566:4566 -p 5500-5524:5500-5524 \
-v /var/run/docker.sock:/var/run/docker.sock \
-v /tmp/mimir-glue:/tmp/mimir-glue \
tanujsoni027/mimir-aws:latest
us-east-1, any local credentials such as test / test.mimir-data Docker volume across restarts and image updates.-e GOKU_SERVICES=all subscribes every service on first start. Every setting is a GOKU_* environment variable, and the former MIMIR_* names still work.RDS runs real PostgreSQL, MySQL and MariaDB. ElastiCache and MemoryDB run Valkey and Redis, DocumentDB runs MongoDB, and Amazon MQ runs RabbitMQ and ActiveMQ. EKS runs k3s, EMR Serverless and Glue run Spark, MWAA runs Airflow, and Lambda and ECS run real containers. That's why the Docker socket mount is needed.
Data endpoints use a dedicated port range that won't clash with a local Redis or Postgres:
-p 5500-5524:5500-5524.latest, v4, 4.0.0: Goku 4.0, multi-arch (linux/amd64, linux/arm64)v3, v2: earlier Mimir releases/var/run/docker.sock (needed for Lambda, RDS, ECS, Glue and the other engine-backed services)8080 (console) and 4566 (AWS endpoint) freeIs Goku a production AWS replacement? No. It's a local development and testing environment.
Does it need an AWS account? No. Everything runs locally.
Can existing AWS SDK code use it?
Yes. Point the SDK at http://localhost:4566.
I use Mimir. Do I need to change anything?
No. goku update (or pulling latest) upgrades in place, and your container, data volume, mimir command and MIMIR_* settings keep working.
Goku is free to use.
Content type
Image
Digest
sha256:1000b2712…
Size
461.3 MB
Last updated
about 2 hours ago
docker pull tanujsoni027/mimir-aws