Reference
Troubleshooting
Fixes for the messages you are most likely to meet: connection failures, access denied, expired sessions, query validation errors, imports that fail and buttons you cannot find.
Connection problems
| Symptom | Cause and fix |
|---|---|
| Connection failed: The security token included in the request is invalid | The profile’s keys are wrong or expired. Run aws sts get-caller-identity --profile <name> in a terminal to verify, then reconnect. |
| Connection failed: Could not load credentials from any providers | No profile matched and the default chain is empty. Create one with aws configure --profile dev or type an existing profile name. |
| Access denied banner in the sidebar | The principal lacks dynamodb:ListTables. Use the banner’s shortcut to Assume Role into a role that has it. |
| Tables from the wrong region | The region selector only offers seven regions. Make sure the one you picked matches your tables; ListTables is regional. |
| Connected to LocalStack but no tables | Check the endpoint port (4566 for LocalStack, 8000 for DynamoDB Local) and that the dynamodb service is enabled in the container. |
Sessions and SSO
| Symptom | Cause and fix |
|---|---|
| Requests start failing after about an hour | An Assume Role session expired and the renewal prompt was ignored. Reconnect or use the renewal dialog next time. |
| SSO: AWS did not recognize this SSO start URL | The SSO region must be where IAM Identity Center is enabled, not where your tables are. |
| SSO: the browser never opens | Click Open the page again. Pop-up blockers and remote desktop sessions sometimes swallow the first attempt. |
| SSO: Your SSO user has no AWS accounts assigned | Sign-in succeeded but no account is assigned to you. Ask your Identity Center administrator. |
Query errors
| Message | Fix |
|---|---|
| ValidationException: Invalid FilterExpression: Attribute name is a reserved keyword | Use a placeholder: #status in the expression and {"#status":"status"} in Expression Attribute Names. |
| ValidationException: Value provided in ExpressionAttributeValues unused | Remove the extra value from the JSON map or reference it in the expression. |
| Query returns nothing for a key you can see | The key is a String that looks numeric and was sent as a Number. Use SQL mode and quote it: WHERE "id" = '001'. |
| Invalid JSON in Expression Attribute Names | The names or values box is not valid JSON. Keys must be double-quoted. |
| Partition key value is required for Query | Fill in the Partition Key value before executing. |
| ProvisionedThroughputExceededException | The table is throttling. Lower Page Size, wait a moment, or raise capacity. |
Tip
Press ⌘+↵ after each fix; the error toast and the inline SQL error clear on the next run.Import and write failures
| Message | Fix |
|---|---|
| Batch n: One or more parameter values were invalid: Missing the key … | Rows lack the partition or sort key under the exact attribute name. Use “Rename to” in the mapping step. |
| Batch n: Type mismatch for key | The key column is typed differently from the table (for example String vs Number). Set the type explicitly in the mapping grid. |
| D deleted, U not processed (throttled) | The bulk delete hit throttling after retries. Re-run the query, reselect and delete again. |
| Item exceeds 400 KB | DynamoDB’s item size limit. Split the item or move large attributes to S3. |
Getting help
Open an issue on GitHub with the app version, your operating system and the exact message you saw. Include the region and whether you were using a custom endpoint; leave out credentials and table data.
Related
Connecting to DynamoDB
The login screen, the four connection methods, Quick Connect with AWS CLI profiles, environment tags, testing a connection and switching or logging out.
Security and privacy
What DynamoOps stores, what it sends and where. Credentials stay on your machine, table data never leaves it, and the app has no account, license check or telemetry.
Contributing
Report bugs, suggest features and send pull requests. These are the conventions that keep the codebase consistent and safe.