Skip to content

Emulators

StackPort only speaks the standard AWS API, so any emulator that implements it can sit behind StackPort. There is nothing emulator-specific to install or enable. You set one URL and StackPort probes every service it knows about; services an emulator does not implement simply show as unavailable on the dashboard.

The emulators below are documented side by side in a fixed order. MiniStack is listed first because StackPort grew out of a MiniStack pull request, not because it is preferred.

EmulatorDefault endpointOne-line startGuide
MiniStackhttp://localhost:4566docker run -d -p 4566:4566 ministackorg/ministackUsing StackPort with MiniStack
Flocihttp://localhost:4566docker run -d -p 4566:4566 floci/flociUsing StackPort with Floci
LocalStackhttp://localhost:4566docker run -d -p 4566:4566 -e LOCALSTACK_AUTH_TOKEN=<your-token> localstack/localstackUsing StackPort with LocalStack
Motohttp://localhost:5000docker run -d -p 5000:5000 motoserver/motoUsing StackPort with Moto

LocalStack needs a LocalStack account and an auth token to start. Its guide covers where to get one.

With the emulator running, start StackPort against it:

Terminal window
AWS_ENDPOINT_URL=http://localhost:4566 stackport # MiniStack, Floci, LocalStack
AWS_ENDPOINT_URL=http://localhost:5000 stackport # Moto

Each guide follows the same structure: setup, a Compose file, what works, and tips specific to that emulator.

Anything that answers the AWS API works the same way. Two common cases:

  • S3-compatible storage such as MinIO: AWS_ENDPOINT_URL=http://localhost:9000 stackport. Only S3 will report as available.
  • DynamoDB Local: AWS_ENDPOINT_URL=http://localhost:8000 stackport. Only DynamoDB will report as available.

For single-service endpoints like these, set STACKPORT_SERVICES to just that service so the dashboard does not probe the rest. See Browse local S3 and DynamoDB.

Leave AWS_ENDPOINT_URL unset and StackPort uses real AWS through your credential chain. See Real AWS and Read-only Mode.

You can register every emulator and account you work with and switch between them from the top bar. See Multiple Endpoints and Authentication.

If a view behaves differently on one emulator than on the others, please open an issue. Closing that kind of gap is exactly what the project wants to do, and pull requests that improve support for any emulator are very welcome.