Installation
Download DynamoOps for macOS or Windows from GitHub, install it and make sure your AWS credentials are ready before the first launch.
Requirements
| Requirement | Details |
|---|---|
| macOS | Apple Silicon (M1 or newer) and Intel, through the universal build. |
| Windows | Windows 10 or 11, 64-bit. Available as an installer or as a portable executable. |
| AWS access | Any of: an AWS CLI profile in ~/.aws/credentials or ~/.aws/config, an IAM Identity Center (SSO) access portal, or a local DynamoDB endpoint. |
| Network | Only needed to reach AWS. Fully offline work against DynamoDB Local or LocalStack is supported. |
| Account | None. DynamoOps is free and has no sign-up or license key. |
| Runtime | Nothing to install. Node.js, the AWS SDK and the local backend ship inside the app bundle. |
aws commands on this machine, you are ready. If not, create a profile as shown below.Install on macOS
- Download the DMG
Get the latest
.dmgfrom the GitHub releases page. Pick the arm64 build for Apple Silicon or the universal build if you are on an Intel Mac. - Drag DynamoOps to Applications
Open the DMG and drag the DynamoOps icon onto the Applications shortcut shown next to it.
- Launch the app
Open DynamoOps from Applications or Spotlight. The first launch shows the login screen with four connection methods: Quick Connect, Saved Profiles, Assume Role and AWS SSO.
Install on Windows
- Download the installer
From the GitHub releases page, download
DynamoOps Setup <version>.exefor a regular install, or the portableDynamoOps <version>.exeto run it without installing. - Run it
Follow the installer, then open DynamoOps from the Start menu. The portable build runs directly from wherever you saved it.
%USERPROFILE%\.aws\credentials and %USERPROFILE%\.aws\config. Run aws configure or create the files by hand.Prepare AWS credentials
DynamoOps never asks you to type an access key. Instead it uses the AWS SDK credential chain on your machine, exactly like the AWS CLI. Pick the method that matches how your team grants access.
- Named profiles. Run
aws configure --profile devor add a block to~/.aws/credentials. You will reference the profile name in Quick Connect. - Assume Role. Keep a base profile with permission to call
sts:AssumeRoleand let DynamoOps assume the target role for you. - IAM Identity Center. You only need your access portal URL. Sign-in happens in the browser and no keys are ever written to disk.
- Local development. Point the custom endpoint at DynamoDB Local or LocalStack. Dummy credentials are injected automatically when no profile is set.
[default]
aws_access_key_id = AKIA................
aws_secret_access_key = ....................
[staging]
aws_access_key_id = AKIA................
aws_secret_access_key = ....................Where DynamoOps stores data
Everything the app persists lives in your user profile. Nothing sensitive is written except the files listed here, and none of your table data is ever stored.
| Data | Location | Contains secrets? |
|---|---|---|
| Saved profiles, recent connections, role history | App local storage | No — identifiers only (region, profile name, role ARN, environment tag) |
| Query history, item version history, theme, cost alert threshold | App local storage | No |
| SSO access tokens and OIDC client registration | ~/Library/Application Support/DynamoOps/sso-cache.json (macOS) or %APPDATA%\DynamoOps\sso-cache.json (Windows) | Yes — owner-only file permissions |
| AWS long-term credentials | ~/.aws/* | Read by the AWS SDK, never copied |
| STS and SSO role credentials | Memory only | Yes — discarded on logout or quit |
Updating and uninstalling
To update, download the new release and install it over the existing app. Your saved profiles and history are preserved. To uninstall, move DynamoOps to the Trash (macOS) or remove it from Apps & features (Windows) and, if you want a clean slate, delete the application data folder listed above.