Skip to content

StackPort: open-source web UI and console for AWS emulators

A web console for your AWS emulator

StackPort shows you what is running in AWS Emulator, MiniStack, Floci, LocalStack, Moto or a real AWS account. Browse 51 services, work in dedicated views for S3, DynamoDB, Lambda, SQS and nine more, call any AWS API from the API Explorer, and learn AWS hands-on with guided lessons.

Free and open source, MIT licensed. pip install stackport or docker run davireis/stackport.

Up and running in a minute

Start the emulator you use, then point StackPort at it. Open http://localhost:8080.

# start AWS Emulator, installed as in AWS's guide
aws-emulator

# start StackPort: it finds the keys and certificate
pip install stackport
AWS_ENDPOINT_URL=https://127.0.0.1:9297 stackport
# start MiniStack
docker run -d -p 4566:4566 ministackorg/ministack

# start StackPort
pip install stackport
AWS_ENDPOINT_URL=http://localhost:4566 \
  AWS_ACCESS_KEY_ID=test AWS_SECRET_ACCESS_KEY=test stackport
# start Floci
docker run -d -p 4566:4566 floci/floci

# start StackPort
pip install stackport
AWS_ENDPOINT_URL=http://localhost:4566 \
  AWS_ACCESS_KEY_ID=test AWS_SECRET_ACCESS_KEY=test stackport
# start LocalStack
docker run -d -p 4566:4566 -e LOCALSTACK_AUTH_TOKEN=<your-token> localstack/localstack

# start StackPort
pip install stackport
AWS_ENDPOINT_URL=http://localhost:4566 \
  AWS_ACCESS_KEY_ID=test AWS_SECRET_ACCESS_KEY=test stackport
# start Moto
docker run -d -p 5000:5000 motoserver/moto

# start StackPort
pip install stackport
AWS_ENDPOINT_URL=http://localhost:5000 \
  AWS_ACCESS_KEY_ID=test AWS_SECRET_ACCESS_KEY=test stackport
# any endpoint that speaks the AWS API:
# MinIO, DynamoDB Local, your own emulator

# start StackPort with the keys it expects
pip install stackport
AWS_ENDPOINT_URL=http://localhost:9000 \
  AWS_ACCESS_KEY_ID=... AWS_SECRET_ACCESS_KEY=... stackport

Every emulator gets the same console, over the standard AWS API, with nothing to install inside it. StackPort began as a web UI pull request to MiniStack, and MiniStack is still its partner project: the two work closely together.

Prefer Docker Compose? Each guide has a Compose setup that runs the emulator and StackPort together, with a seed that creates demo resources. Already have an emulator running elsewhere? Any AWS-compatible endpoint works.

What you get

Everything runs locally, talks the standard AWS API, and needs no setup inside your emulator

51 services, one dashboard

Every service probed in parallel, with resource counts that update live over a WebSocket. Services your endpoint doesn’t have are marked as not supported, and the ones you star move to the top.

13 dedicated views

S3, DynamoDB, Lambda, SQS, SNS, EC2, IAM, RDS, KMS, Step Functions, CloudWatch Logs and Metrics, and Secrets Manager. Everything else gets a searchable table with JSON details.

API Explorer

Call any operation of any service boto3 knows, from a form built from the API’s own model. Copy the same request as an AWS CLI command or boto3 code.

Guided lessons

Learn AWS hands-on without an AWS account or a bill. Lessons run inside the console and check your real resources, so a step turns green when the thing exists.

Make changes, not just look

Upload to S3, edit DynamoDB items, send SQS messages, publish to SNS, invoke Lambda, start Step Functions executions, tail logs live.

Real AWS, read-only when you want

Browse an account through your profile, SSO or keys. Set STACKPORT_ALLOW_WRITES=false and the server refuses every write.

Many endpoints at once

Register emulators and accounts side by side, each with its own region, credentials and certificate settings, and switch from the top bar.

pip, Docker and a CLI

One Docker image for amd64 and arm64, or a plain pip install. The same package has a CLI (status, list, describe, export) for scripts and CI.

Built for daily use

Keyboard shortcuts, deep links to any resource, JSON and CSV export, and light and dark themes. Press ? to see the shortcuts.

See it in action

Views built around how you actually use each service

StackPort dashboard in the dark theme, connected to AWS Emulator, with 51 of 51 services available and a card for each one showing its resource countsStackPort dashboard in the light theme, connected to AWS Emulator, with 51 of 51 services available and a card for each one showing its resource counts
Dashboard: every service with live resource counts
S3 browser with folders, objects and upload
S3: folders, drag and drop upload, bucket settings
DynamoDB browser showing table items
DynamoDB: scan, query and edit items as JSON
Lambda browser showing function configuration
Lambda: configuration, invoke with event templates
SQS browser with queues and message counts
SQS: send, poll, purge and saved messages
Step Functions graph with an execution path
Step Functions: state machine graph and execution path
KMS browser showing a key with its policy
KMS: keys, policies, grants and aliases

Learn AWS without an AWS account

Guided lessons run inside StackPort against your own emulator, so there is no account to create and no bill to worry about. A panel walks you through each step while markers point at the real controls.

  • Do each step in the console or with the AWS CLI, with commands already filled in.
  • StackPort checks the live state, so a step turns green when the resource really exists.
  • Skip anything, come back later. Nothing is a gate.
How guided lessons work
A guided lesson in the Learn panel next to the S3 view
The API Explorer running a DynamoDB Scan: the operation list with Read and Write badges, a form for the request, and the JSON response with its status and request ID

Call any AWS API, even without a view

Emulators implement far more than any console can show. The API Explorer reaches every operation of every service boto3 knows, against the endpoint you have selected.

  • A form built from the operation’s own model, with a JSON view of the whole request.
  • The response as JSON, with its status, request ID and timing, and errors in the endpoint’s own words.
  • The same request as an AWS CLI command or boto3 code, with any setup your emulator needs.
How the API Explorer works

51 AWS services

Dedicated views highlighted. Every other service gets a searchable resource table, and the API Explorer reaches the rest.

S3DynamoDBLambdaSQSSNSEC2IAMRDSKMSStep FunctionsCloudWatch LogsCloudWatch MetricsSecrets ManagerACMAPI GatewayAppConfigAppSyncAthenaBatchBedrockCloud MapCloudFormationCloudFrontCloudTrailCodeBuildCodeCommitCodeDeployCodePipelineCognito User PoolsCognito IdentityECRECSEFSEKSElastiCacheElastic Load BalancingEMREventBridgeEventBridge PipesEventBridge SchedulerFirehoseGlueKinesisMSKOpenSearchRoute 53SESSSM Parameter StoreVerified PermissionsWAFv2X-Ray

Questions people ask

Short answers, with links to the details

Is there a UI for AWS Emulator?

AWS Emulator itself has no graphical interface: you use it through the AWS CLI and SDKs. StackPort is an independent, open-source web console that works with it. Start StackPort with AWS_ENDPOINT_URL=https://127.0.0.1:9297 stackport and it finds the keys and certificate the emulator writes to ~/.aws/emulator/<port>/ by itself. See Using StackPort with AWS Emulator.

Does StackPort work with MiniStack, Floci, LocalStack and Moto?

Yes. StackPort talks to every emulator over the standard AWS API, so there is nothing to install inside it, and any other AWS-compatible endpoint works too. MiniStack is StackPort's partner project: StackPort started as a web UI pull request to MiniStack. Each emulator has its own guide: MiniStack, Floci, LocalStack and Moto.

Is StackPort an emulator?

No. StackPort doesn't emulate AWS. It is a console and API client: it shows you what your emulator, or a real AWS account, holds, and lets you change it.

Is it safe to use with a real AWS account?

StackPort can browse a real account through your profile, SSO or access keys, and shows a warning banner on every page while it does. Writes stay enabled unless you set STACKPORT_ALLOW_WRITES=false; then the server refuses every request that would change AWS. Lambda Invoke stays available, and it runs your function's code. StackPort has no login, so it only listens on your own machine (127.0.0.1) unless you open it up, and a read-only IAM role adds a second layer. See Real AWS and Read-only Mode.

Does StackPort send data anywhere?

No. StackPort has no telemetry or analytics. Its server only talks to the endpoints you configure (for a real AWS endpoint, that is AWS and wherever your credentials come from, such as SSO), and the web UI only talks to the StackPort server. Endpoints you add and your lesson progress are saved on your machine, in ~/.stackport.

Is StackPort made by AWS or by an emulator project?

No. StackPort is an independent, MIT-licensed open-source project and is not affiliated with or endorsed by AWS. MiniStack is its partner project. Contributions that improve support for any emulator are welcome on GitHub.

How do I install it?

Run pip install stackport (Python 3.10 or newer) and then stackport, or run the davireis/stackport Docker image, and open http://localhost:8080. See Installation.

Give it a try

StackPort is free and open source, built in the open with the emulator community. If it saves you a few aws --endpoint-url commands, a star on GitHub helps other people find it.

StackPort is an independent, open-source project (MIT). It is not affiliated with or endorsed by Amazon Web Services. MiniStack is its partner project; other emulator names belong to their own projects. AWS is a trademark of Amazon.com, Inc. or its affiliates.