dynobase-icon
Dynobase
New in 3.0
Pricing
Learn
Support

GUI for DynamoDB Local, LocalStack, and Docker

Prerequisite:   Download Dynobase (free to try) in order to follow the steps below

Dynobase connects to DynamoDB Local and LocalStack through a configured endpoint. You can browse, query, and edit local tables from the same desktop workspace as AWS tables. Start the local service first, then match the endpoint and local credentials used to create your tables.

The demo shows an earlier interface. The written steps describe Dynobase 3.0.8.

1
Start the local service

Run DynamoDB Local or LocalStack, directly or in Docker, and note its exposed HTTP endpoint. The container port and the host port must match your connection settings.

2
Configure Offline Settings

Open Settings and Offline Settings. Configure the port or local endpoints, Regions, and Override Access Key when your local database requires matching the credentials used to create its tables.

3
Select the local profile

Save the settings and select the local endpoint profile. Run a query or scan to verify connectivity before importing or changing data.

Frequently Asked Questions

What is DynamoDB Local?

DynamoDB Local is AWS's downloadable development and testing database with support for many DynamoDB APIs. It does not reproduce every managed-service feature or production behavior; see local setup and differences.

Why use a GUI with DynamoDB Local?

A GUI lets you inspect items, run queries, and edit test data without writing a script for each action. The old DynamoDB Local JavaScript web shell is deprecated; Dynobase supplies a desktop interface.

Which Dynobase workflows work locally?

Use supported item reads and writes, visual filters, favorites, history, and code generation against the local endpoint. Cloud-only features such as managed backups and S3 export still require the AWS service.

How does LocalStack differ from DynamoDB Local?

DynamoDB Local focuses on DynamoDB APIs, while LocalStack emulates multiple AWS services for integration testing. Feature coverage depends on the installed version and configuration; neither is a substitute for checking production behavior in AWS.

Why is my local profile missing?

Check that the endpoint is running and included in Offline Settings. DynamoDB Local commonly uses port 8000 and LocalStack uses port 4566; use your actual exposed host port if you changed it.

Why is the profile visible but the tables are missing?

Check the endpoint, Region, and access key used when the tables were created. Without -sharedDb, DynamoDB Local separates database files by access key and Region; configure the same values or deliberately use a shared database.

Product Features

DynamoDB Tools

DynamoDB Info

DynamoDB Guides

Download
/
Pricing
/
Member Portal
/
Privacy
/
EULA
/
Twitter
© 2026 Dynobase