Dynobase hangs on profiles loading screen or profiles are loading slow

If you are using Dynobase and you are seeing the following screen after launching it:

Here are the steps you can take to solve this issue:

1. Make sure you have the latest version of Dynobase. The best way to check it is to go to Dynobase's Releases page on Github and downloading the latest release for your platform.

2. Make sure your router or firewall is not blocking AWS requests. You can check if you can connect to the AWS by running the following command:

aws sts get-caller-identity --profile <PROFILENAME>
aws sts get-caller-identity --profile <PROFILENAME>

or

aws dynamodb list-tables --profile rafal-personal
aws dynamodb list-tables --profile rafal-personal

3. If you're having multiple profiles on your computer in the ~/.aws directory, you can exclude some of them from being loaded by the Dynobase by adding the dynobase_skip=true line, for example:

[profile profile-not-for-dynobase]
region=us-east-1
output=json
dynobase_skip=true
[profile profile-not-for-dynobase]
region=us-east-1
output=json
dynobase_skip=true

Alternatively, you can go do General Settings and type included profiles there. The best practice is to reduce the amount of profiles that Dynobase should load to the minimum - because Dynobase by default loads and verified all the profiles in the ~/.aws directory, excluding some of them can reduce the time it takes to load.

4. Exclude unused regions. If all the tables you're using are in e.g. region us-east-1, there's no point for Dynobase to look for them in other regions. To do so, go to General Settings and select regions you'd like to skip during the loading procedure:

It should speedup the loading process significantly.

5. If there's something running on the port 8000 on your machine, change Dynobase's DynamoDB Offline port setting to something else because otherwise Dynobase will try to connect to that port assuming it's local DynamoDB distribution.

More resources:

• Using Dynobase with SSO profiles
• Using Dynobase with aws-vault
• Using Dynobase with DynamoDB Local