NoSQL Workbench not adding account when including Role ARN

It sounds like you're experiencing an issue with NoSQL Workbench when trying to connect using a role ARN. Based on the information provided, here are some potential solutions:

1. When connecting to DynamoDB using NoSQL Workbench, the basic connection requires an account alias, AWS Region, access key ID, and secret access key. The role ARN appears to be causing the issue in your case.

2. Since the connection works without the role ARN but fails when you include it, this suggests either:

• There might be an issue with the trust relationship between your IAM User and the role
• The permissions for assuming the role might be missing

3. Try these troubleshooting steps:

• Double-check the role ARN format to ensure it's correct
• Verify that the trust policy on the role explicitly allows your base account/user to assume it
• Confirm that your base user credentials have the necessary "sts:AssumeRole" permission on the target role ARN
• Try using temporary credentials (with a session token) that already have the necessary DynamoDB permissions instead of role assumption
• Check for AssumeRole events in CloudTrail to look for exceptions and errors.

Sources
Connecting to live datasets - Amazon DynamoDB