Error accessing AWS.SharedIniFileCredentials when credentials file does not exist

[awschristou]

Confirm by changing [ ] to [x] below to ensure that it's a bug:

• I've gone though Developer Guide and API reference
• I've checked AWS Forums and StackOverflow for answers
• I've searched for previous similar issues and didn't find any solution

Describe the bug
If you have a config file and no credentials file, you get an ENOENT error against the credentials file when attempting to load a shared credential.

Is the issue in the browser/Node.js?
Node.js

If on Node.js, are you running this on AWS Lambda?
No

Details of the browser/Node.js version
Paste output of npx envinfo --browsers or node -v
v10.15.1

SDK version number

• For Node.js, get SDK version by
  • running command npm list aws-sdk from your root directory
    [email protected]

To Reproduce (observed behavior)
Steps to reproduce the behavior (please share code or minimal repo)

• Set up shared credentials
  • Set up a valid config file
  • Have no credentials file
• Try to access a profile with the SDK
  • from a typescript file, I have

new AWS.SharedIniFileCredentials({profile: profileName})

• Error occurs

Expected behavior
SDK handles this without error.

[AllanZhengYP]

Hey @awschristou,

This is intentional. You need to set AWS_SDK_LOAD_CONFIG environmental variable to be able to load credentials from config file. This is due to some backwards compatibility concern, see #1391 for more information.

If you don't set it, SDK will assume there is no config file when loading the credentials. That's why you see credentials loading failed.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.