ENOENT error when there is a config file but not a credentials file present

If shared credentials are set up in the config file, and no credentials file is present, the toolkit brings up an error message when trying to connect to AWS. Users are unable to connect to AWS unless they make an empty credentials file in the .aws folder at the very least.

This was demonstrated on OSX

[thomasmichaelwallace]

@justinmk3 yes- the fix was designed for the case where you wanted to only use a config file with no credentials. I use it myself in production (on osx and linux).

To help debug, can I invite you to work through the following response to someone else who '@'d me about the fix: https://github.com/aws/aws-sdk-js/issues/3436#issuecomment-727180538

Assuming that this toolkit (which I do not use) isn’t doing anything too exciting, I suspect your environment is either not setup correctly, or is not being carried over into vscode.

As a hunch, your debugging may reveal a separate bug that the sdk requires a credential file to resolve the region. But, at present, that’s pure speculation on my part. 😄

[justinmk3]

• Toolkit 1.23 includes https://github.com/aws/aws-toolkit-vscode/pull/1626 which should fix this.
• Confirmed with d189dd58e800 after removing ~/.aws/credentials file.

The following prerelease build includes the fix, we appreciate your feedback:

1. Download/extract the prerelease build: aws-toolkit.zip
2. From the VSCode command list (ctrl-shift-p or cmd-shift-p) run Extensions: Install from VSIX... to install the *.vsix file.
3. Reload VSCode and verify that the Toolkit has the new version (not the release/older version).