New in 4.3

Twelve new services that really run, and 80% of AWS's operations. EFS, WAF, Timestream, IAM Identity Center, CodeCommit, Managed Flink, DMS, EMR on EC2 and more; pipelines that run, EC2 disks with real data, live RDS replication and Airflow 3. See what's new.

New name

Mimir is now Goku, everywhere. Every name is Goku now: the image tanujsoni027/goku, the goku container and command, and GOKU_* settings. Existing installs move over automatically and the old names keep working for now, so start using the goku names.

What's new in Goku 4.3 →

Goku — Your Local AWS Cloud

Goku (formerly Mimir) is a local AWS cloud emulator: 87 AWS-compatible services — S3, Lambda, DynamoDB, RDS, Step Functions, API Gateway, Glue and more — on localhost:4566, with a web console for 70 services on localhost:8080, real container-backed engines, and zero AWS account. Free.

Install Goku What's new in 4.3
$ curl -fsSL https://tanuj24.github.io/goku/install.sh | sh

Then run goku start and open http://localhost:8080 — click “Load sample data” on any console page to explore a populated cloud.
Or run it with Docker directly — see all install options. Needs Docker Desktop on macOS and Windows, or Docker Engine or Docker Desktop on Linux.

87AWS-compatible services
70console services
$0.00everything free
amd64 + arm64multi-arch image
Release notes · 4.3.0

What's new in Goku 4.3

Goku 4.3 is the biggest release yet. Twelve new services run for real, from Amazon EFS and AWS WAF to Managed Service for Apache Flink, DMS and EMR on EC2. Pipelines run their stages, EC2 disks hold real data, RDS replicas follow their source live, and MWAA runs Airflow 3 with Celery workers. Goku now answers 5,162 of 6,441 AWS operations (80%) across 87 services.

Twelve new services that really run

Amazon EFS file systems with real files, AWS WAF web ACLs that filter real traffic, Amazon Timestream with its SQL, IAM Identity Center with a working access portal, IAM Access Analyzer, AWS CodeCommit Git repositories you clone and push to, Managed Service for Apache Flink, AWS DMS, Amazon EMR on EC2, MWAA Serverless, CloudFront KeyValueStore and AppSync Event APIs.

Data moves for real

DMS tasks copy MySQL, MariaDB, PostgreSQL and S3 data into databases, S3, Kinesis, DynamoDB or OpenSearch, then keep replicating changes. Flink applications run your jar on a real Flink cluster. EMR clusters run Spark steps on real nodes. RDS read replicas and blue/green deployments of MySQL, MariaDB and PostgreSQL replicate live, and a switchover loses no write.

Pipelines and Airflow 3

CodePipeline runs its stages on Goku's own services: a push to CodeCommit or ECR, or a new S3 object, starts it, CodeBuild builds in real containers, and CloudFormation, ECS, CodeDeploy and S3 deploy, with manual approvals and Lambda and Step Functions actions. MWAA runs the Airflow versions MWAA offers today, Airflow 3 included, with Celery workers that scale with your tasks and real version upgrades.

More in 4.3

Before you update

Update with Update now in the console, or run goku update --cli and then goku update. Running Goku 4.1 or later shows the update by itself.

Release notes · 4.2.3

Earlier: Goku 4.2

4.2.3: RDS runs the database versions AWS offers today. Each engine version now runs exactly that version, and new databases default to PostgreSQL 18.6, MySQL 8.4.11 and MariaDB 12.3.3. Upgrade a database to a newer version from the console or with ModifyDBInstance: its data, users and passwords move with it, and if the new version does not come up the old one comes back on the untouched data. Databases created on earlier releases keep the engine that created their data and show the version they really run.

4.2.2: Every engine that cannot start now says why. An RDS instance, Redshift cluster, OpenSearch domain, EKS cluster, ElastiCache or MemoryDB cluster, DocumentDB or Neptune cluster, Amazon MQ broker or MWAA environment whose engine exits, runs out of memory or never becomes ready fails at once with the engine's own error, in its status, its events and the console, with a link to the engine's logs. Nothing stays creating forever, and PostgreSQL, MongoDB, RabbitMQ and Valkey keep their data in Docker volumes where the data folder does not keep owners and permissions (a Windows drive, for one). Thanks to the user who reported their RDS instances failing without a reason.

4.2.1: Amazon MSK now works on macOS and Windows: Kafka brokers keep their data in a Docker volume where the data folder is a Docker Desktop file share, and data from a cluster that already ran is copied over. Brokers are reachable from your machine at the localhost address GetBootstrapBrokers returns, a cluster whose broker cannot start moves to FAILED and says why, and goku services subscribe msk works. Thanks to the user who reported these. Update with goku update or Update now in the console.

Goku 4.2 answers 73% of the AWS operations it emulates, up from 42%: Glue, the core services and every data service are now complete. Workspaces let you run only the services you're working with today and pause or stop the rest to save memory. And the IAM Lab can show what any role in your real AWS account can do, using the AWS profile you already have.

Workspaces: only what you use today

Save the services you work with together, such as “Serverless day” (Lambda, ECS, DynamoDB) or “Data day” (Glue, S3, Athena), then Start, Pause, Stop or Switch to them as one. Pause keeps the containers' memory and uses no CPU; Stop frees the memory and keeps the data. How workspaces work.

See what an AWS role can do

IAM Lab → Role access connects to your AWS account with a profile you already have: access keys, SSO or assume-role, with no role to deploy. Pick a role to see every action it is allowed and the statement behind it, who can assume it in plain words, and its risks. Read-only, always. See a role's permissions.

goku CLI 0.6.0 and MCP

goku ws starts, pauses, stops and switches workspaces from your terminal, and goku iam profiles, connect, roles and access ROLE show what a role can do. Nine new MCP tools let AI assistants do both, 34 in total.

The Workspaces page in the Goku console: running, paused and stopped workspaces with their services, containers, memory and CPU
Workspaces. Every workspace with its state, services, memory and CPU, live, and one-click Start, Pause, Stop or Switch. Workspaces guide
The AI assistants (MCP) page in the Goku console with the MCP endpoint and copy-paste setup for Claude Code, Claude Desktop, Cursor and VS Code
AI assistants (MCP). Connect Claude Code, Cursor, VS Code and others to your local AWS: 34 tools, now including workspaces and role access. MCP guide
The workspace switcher in the Goku console top bar listing workspaces with their state and Start, Pause, Stop and Switch actions
The switcher in the top bar. Switch to another workspace from any page. Pause keeps memory; Stop frees it.
The IAM Lab role access page in the Goku console showing an AWS role’s allowed actions per service, with resource scope and conditions
What an AWS role can do. Every action a role in your AWS account is allowed, per service, with the policy statement behind it. Role permissions guide

4,255 of 5,849 AWS operations: 73%, up from 42%

Goku 4.2 adds 1,820 operations. Each one keeps real state and follows AWS's request and response shapes, errors and paging.

The Service coverage page in the Goku console: 4,255 of 5,849 AWS operations implemented, 442 partial, with API Gateway, Redshift, RDS, Systems Manager, OpenSearch and Cognito at 100%
Service coverage in the console: search any AWS operation to see whether Goku answers it, and what is partial.
ServiceGoku 4.1Goku 4.2
Glue107 / 300299 / 300
Systems Manager23 / 152152 / 152
CloudWatch Logs27 / 118117 / 118
IAM100 / 180178 / 180
Cognito user pools57 / 132132 / 132
CloudFormation27 / 9089 / 90
Athena13 / 7070 / 70
API Gateway (REST, HTTP and WebSocket)125 / 227227 / 227
Lambda54 / 8888 / 88
S371 / 116116 / 116
RDS39 / 164164 / 164
Redshift and Redshift Serverless87 / 210210 / 210
OpenSearch and the Elasticsearch Service API24 / 147147 / 147
EKS7 / 7070 / 70

ECR, AWS Backup, ElastiCache, Transfer Family, Neptune, MSK, KMS, Secrets Manager, STS, CloudWatch, EventBridge, Step Functions, Kinesis, Firehose, ECS, DynamoDB, SNS, DocumentDB, MemoryDB and Lake Formation are complete too.

Highlights, all running against your local data

A few of the new operations:

Answers that now match AWS

Some answers changed to match AWS's behaviour, so code that relied on the old ones may notice:

Also in 4.2: images pushed to an ECR repository's URI with docker push now show up in DescribeImages and ListImages, with a registry front that keeps each account's and Region's images apart, and the last Mimir names users could see, such as the images and S3 buckets Goku creates, are Goku names now. Nothing needs to be rebuilt or re-created.

Release notes · 4.1.0

Earlier: Goku 4.1

Goku 4.1 connected AI assistants to your local AWS. Goku serves the Model Context Protocol at http://localhost:8080/mcp, so Claude Code, Claude Desktop, Cursor, VS Code, Windsurf and any other MCP client can create and inspect resources, call any AWS API, read logs, take snapshots and inject faults, all against the sandbox on your machine. goku CLI 0.5.0 added goku mcp, a stdio bridge that starts Goku when it isn't running, and goku mcp config prints the setup for each client. Connect an AI assistant to Goku.

Release notes · 4.0.0

Goku 4.0

Mimir is now Goku, everywhere. Goku tells you when a new version is out and updates itself from the console, and everything it keeps, including your databases, lives in a folder on your disk. It also adds AWS Glue 6.0, DynamoDB vector search, AWS Lambda runtime parity, a rebuilt ECS, the IAM Policy Lab, a lightweight start with per-service subscriptions, a Resource Center, real engines behind a dozen more services, and console pages for 33 more services — 60 in total, on a backend of 73.

Mimir is now Goku, everywhere. Start using the goku names.

Every name is Goku now: the image tanujsoni027/goku, the goku container and command, GOKU_* settings, /_goku paths, goku.local host names and the goku-ca.pem file. The site moved to tanuj24.github.io/goku.

Update now, from the console

The console shows when a new version is out. One click downloads it and replaces the running Goku with the same ports, settings and data; if the new version doesn't come up healthy within 3 minutes, Goku rolls back to the one you had. The check is one download of a static file, with nothing about you sent; GOKU_UPDATE_CHECK=off turns it off.

Everything in a folder on disk

Buckets, tables, functions and the data of every engine (RDS PostgreSQL databases, OpenSearch, ECR, DocumentDB, MemoryDB, Amazon MQ and Redshift) live in ~/.goku/data (%LOCALAPPDATA%\Goku\data on Windows). On macOS and Windows, MSK and RDS MySQL keep their data in Docker volumes, which also survive restarts and updates, and so do PostgreSQL, MongoDB, RabbitMQ and Valkey where the data folder does not keep owners and permissions (a Windows drive, for one). Reset Docker, update or reinstall: start Goku with the same folder and resume where you left off. Existing data moves in by itself.

goku CLI 0.4

goku update moves your install to the data folder on the way; goku update --cli updates the CLI itself, verified against its published checksums; goku data shows, opens or migrates the folder. The CLI tells you, at most once a day, when a new Goku or CLI is out.

Coming from Mimir?

Install the CLI and run goku update: it saves your state, moves it into the data folder, renames your mimir container to goku and starts the newest Goku on the same ports. Your old mimir-data volume stays as a backup. Using plain Docker? See upgrading an existing install.

AWS Glue 6.0

Glue 6.0 (Spark 4.1.1, Python 3.13, Java 17) and Glue 5.1, per job or notebook. AWS publishes no Glue 6.0 image, so Goku builds one locally the first time a 6.0 job runs — a one-time step of a few minutes. New jobs default to Glue 5.1, as on AWS.

DynamoDB vector search

The VectorIndexes and SearchVectors APIs with cosine, Euclidean and dot-product distance, and a console tab to search by text, by a similar item or by raw vector. Plus a rebuilt item explorer and a PartiQL editor.

Lambda runtime parity

Every runtime AWS Lambda supports today — Node.js, Python, Java, .NET, Ruby and provided.al2023 — on arm64 and x86_64, with AWS's lifecycle dates. Also provisioned concurrency, SnapStart, container-image functions and response streaming.

A rebuilt ECS

Self-healing services, rolling deployments and a circuit breaker with rollback; health checks, secrets and volumes; ECS Exec from the AWS CLI, Service Connect and AWS Cloud Map; and a browser terminal into running containers.

IAM Policy Lab

Answers “if I ship this IAM change, who gains or loses what access, and why?” before you ship it: effective access with evidence, policy drafts you can diff, simulate and size by blast radius, and IAM tests with regression reports — for Goku or, read-only, a real AWS account.

Start light, subscribe to what you use

A new installation starts only the core services — S3, DynamoDB, Lambda, SQS, SNS, IAM/STS, CloudWatch, KMS, Secrets Manager and Systems Manager. Subscribe to more, or to a preset such as Containers, Databases or Analytics, on the Services page.

Resource Center

Everything Goku runs — databases, brokers, clusters, functions and build containers — with live memory and CPU. Pause, stop, restart or remove any of it from one place, with a memory budget, idle auto-stop and disk cleanup.

Real engines for a dozen more services

Bedrock through a local Ollama, Redshift and its Data API, Amazon MWAA on real Airflow, EMR Serverless on real Spark, MemoryDB on real Valkey, DocumentDB on real MongoDB and Amazon MQ on real RabbitMQ or ActiveMQ.

33 more console pages

60 in total. New pages include Route 53, Elastic Load Balancing, CloudFront, CodeBuild, CodeDeploy, AWS Backup, AWS Config, Bedrock, Cost Explorer, Redshift, Amazon MWAA, CloudTrail, X-Ray and AWS Organizations.

Build, test and debug faster

New developer tools, in the console, the API and the goku CLI:

Also new in 4.0: real engines behind a dozen more services — including Bedrock through a local Ollama, Redshift, Amazon MWAA on real Airflow, EMR Serverless on real Spark, MemoryDB, DocumentDB and Amazon MQ — and console pages for 33 more services, from Route 53 and CloudFront to Cost Explorer and AWS Organizations.

Live execution

Watch Step Functions run — locally

A real-time workflow graph: states color in as the execution progresses, Choice branches show their conditions, and Task nodes deep-link to the local resources they invoke.

AWS Step Functions running locally with a live workflow graph in the Goku console
Every service, a real console

Pick a service, see its console

A tour of the bundled web console: 27 of its 70 service consoles, grouped the way AWS groups them, plus Goku's own tools, with Workspaces and IAM Role access new in Goku 4.2. Click any one to see its page.

Storage
Databases
Compute
Containers
App Integration
Analytics
Security & Identity
Management
Observability
Goku tools
S3 console in Goku — local AWS S3 emulation

Storage · S3 console in Goku

Console

70 AWS service consoles, one image

The bundled web console covers 70 services, and every service page has a one-click “Load sample data” button, so you can explore a populated cloud in under a minute.

Goku web console home with local AWS services: S3, DynamoDB, Lambda, SQS, SNS, CloudWatch, EC2, ECS, EKS, Glue and more
Features

What you get

Real engines, not mocks

RDS starts a real PostgreSQL, MySQL or MariaDB container — connect with psql on localhost:5500. ElastiCache and MemoryDB run real Redis or Valkey, DocumentDB runs real MongoDB, Amazon MQ runs real RabbitMQ or ActiveMQ, OpenSearch is the real engine and EKS boots real k3s. Lambda functions run in real runtime containers.

API Gateway you can curl

Build REST, HTTP and WebSocket APIs in the console, attach a Lambda integration, and invoke them on localhost seconds later — no deploy pipeline, no waiting.

Glue that actually runs

Real PySpark jobs and interactive notebooks with the real awsglue libraries, Glue 6.0 back to 2.0, with Hudi, Delta Lake and Iceberg. Step Functions Task states really invoke your local Lambdas.

Everything on disk

Your buckets, tables, functions and jobs, and the data of every database and broker, live in a folder on your disk. Stop, update, reinstall or reset Docker: start Goku with the same folder and carry on.

No port roulette

Data endpoints live in a dedicated 5500–5689 range, so they never clash with a local Redis, Postgres or Elasticsearch. RDS, ElastiCache and Neptune use the published 5500–5524 ports; the rest bind on your host automatically.

CloudWatch everywhere

CloudFormation stacks actually provision the buckets, queues and topics in your template, and every container-backed service streams logs to its AWS-convention CloudWatch log group, exactly like the real cloud.

Zero code changes: point your AWS CLI, SDK or app at http://localhost:4566, region us-east-1, with any local credentials such as test / test — or let goku env set it all for you.

Guides

Guides: run and test AWS locally

Step-by-step walkthroughs with commands you can paste, for the things developers most often run locally.

Run AWS locally without an account

Install Goku, point the AWS CLI at localhost:4566 and create S3 buckets, DynamoDB tables, SQS queues and Lambda functions on your machine.

Test AWS Lambda locally

Create, invoke and debug functions in real runtime containers, read their CloudWatch logs and stop on breakpoints in VS Code or JetBrains IDEs.

DynamoDB on your machine

Tables, items, GSI queries, PartiQL, Streams and vector search on localhost, with your data kept between restarts.

Run AWS Glue jobs locally

Glue 6.0 and 5.1 jobs and notebooks on real Spark with the awsglue libraries, a local Data Catalog and S3.

Connect AI assistants to local AWS

Give Claude Code, Claude Desktop, Cursor, VS Code or Windsurf 34 tools and any AWS API call on a local sandbox, never your real AWS account.

Run only the AWS services you need

Save the services you work with as workspaces and start, pause, stop or switch them together, so only what you use today takes memory.

See what an AWS IAM role can do

Connect the IAM Lab with an AWS profile you already have and see a role's effective permissions, who can assume it and its risks, read-only.

FAQ

FAQ

Goku was formerly Mimir. What changed?

Only the name. Goku is the same product, renamed in Goku 4.0, where every name became Goku: the image tanujsoni027/goku, the goku container and command, GOKU_* settings, /_goku paths and goku.local hostnames. Existing installs move over automatically, and the old Mimir names keep working for now, so start using the goku names. See old and new names.

How do I run AWS locally without an AWS account?

Install Goku and point your AWS CLI or SDK at http://localhost:4566, region us-east-1, with any local credentials such as test / test — goku env sets these for you. No account and no sign-up. Once the image and any runtime images your services need are pulled, everything runs on your machine without internet access. Walkthrough: how to run AWS locally.

Can I test and debug Lambda functions locally?

Yes. Functions run in real runtime containers for every runtime AWS Lambda supports today, with logs, versions, aliases, function URLs and event source mappings. Step through a handler from VS Code, IntelliJ, PyCharm or GoLand. See testing AWS Lambda locally.

Can I run only the AWS services I need, to save memory?

Yes. Save the services you work with together as a workspace, for example Lambda, ECS and DynamoDB, and start, pause, stop or switch them as one from the console, goku ws or MCP. Pause freezes the containers: they keep their memory and use no CPU. Stop frees the memory and keeps the data. See running only the services you need.

Can Goku show what a role in my real AWS account can do?

Yes. The IAM Lab connects to your AWS account with an AWS profile you already have (access keys, SSO or assume-role), scans its roles with read-only calls and shows for any role every action it is allowed, who can assume it and its risks. Nothing in the account changes, and credentials are held in memory only. See what an AWS IAM role can do.

Does my data survive restarts and updates?

Yes. Everything Goku keeps, databases included, lives in a data folder on your disk (~/.goku/data, or %LOCALAPPDATA%\Goku\data on Windows). It survives stops, updates, reinstalls and Docker resets. Environment snapshots can save and restore the whole local cloud.

Does Goku run on Windows and Apple Silicon?

Yes. The goku CLI installs natively on macOS, Linux and Windows and runs Goku in Docker. The image is multi-arch (arm64 + amd64), so it runs natively on Apple Silicon.

What do I need to run Goku?

Docker: Docker Desktop on macOS and Windows, and Docker Engine or Docker Desktop on Linux. See all install options.

Is Goku a production AWS replacement?

No. Goku is a local development and testing sandbox — build and iterate locally, then deploy to real AWS for production.