Missing credentials error when connecting to remote dynamoDB using NoSql Workbench

Hello,

This error - Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 generally indicates an issue with the tool not being able to pick up the credentials from the Config/Credential file.

To troubleshoot the issue here, I would recommend you to check the following -

1. In aws folder of your system, check for the existence of config and credentials file.

   • However, I did notice you mentioned that you have a config and credentials file setup on my Mac.

2. Next, you should check that there exists profile like default etc in your config/credential files for example -

   • In ~/.aws/credentials

   [default]
   aws_access_key_id = AKIA..........1
   aws_secret_access_key = 9A......................tr2
   

   • Important note - In case if you are leveraging temporary IAM Role access credentials instead of IAM User long term access credentials, then please make sure that the temporary access credentials are not expired. For more information, you can see here.

3. After this, I would also recommend checking that the above long term access key credentials actually are in ACTIVE status and not inactive.

   • You can query this information by checking the access keys under the Security credentials tab of your IAM User on AWS Console.

   https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey

4. Also, I would highly suggest to check if your credentials/config file are working for other tools/SDK to isolate if the behavior is seen for a specific tool only or if it's consistent in other tools as well.

   • You can do this by running a simple AWS CLI command like - aws s3 ls to see if your credentials (from config/credential file) are being leveraged by AWS CLI or not for calling the AWS service APIs. If you are able to run the commands successfully on AWS CLI without triggering the same error, then we can isolate the issue to your installed tool itself. In this case scenario, I would recommend reaching out to this tool's support team directly on this issue.
   • However, in case if your AWS CLI also fails with the same error, then I would request you to raise a support case with our IAM Premium Support team so that we can dive deeper on your environment, and check the credentials to see what might be causing the above error.
   • Please do not post any sensitive information (such as credential access keys) over re:Post since this is a public platform.

   AWS CLI install and update instructions - https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html#getting-started-install-instructions