Credentials profile is invalid while trying to Connect to AWS

[hilalhmuhammed]

Describe the bug
Installed AWS toolkit for VS Code, I have my config and credentials file with the following key and their values
config

[default]
region = us-west-2

credentials

[default]
AWS_ACCESS_KEY_ID=<key>
AWS_SECRET_ACCESS_KEY=<secret>
AWS_SESSION_TOKEN=<token>

Clicking on Connect to AWS using default profile will pop an error dialogue that says Credential profile default is invalid
To Reproduce

Expected behavior
Connection successful to AWS

Screenshots

Desktop (please complete the following information):

• OS: Windows 10 Enterprise, Build 1803 (x64)
• Visual Studio Code Version: 1.36.1
• AWS Toolkit for Visual Studio Code Version: 1.0.0

Additional context
Have tried using a named profile instead of default, the error persist

[awschristou]

Hi @hilalhmuhammed thank you for reaching out. Can you please try setting the keys in your credentials file to lowercase, then restart VS Code, and let us know if you have the same result?

[default]
aws_access_key_id=<key>
aws_secret_access_key=<secret>
aws_session_token=<token>

[jmery]

@awschristou Trying this toolkit for the first time and am having the same error. Both my config and credentials files are lowercase:

config

[profile personal]
region = us-west-2

[profile sa]
region = us-west-2

credentials

[personal]
aws_access_key_id = <key>
aws_secret_access_key = <secret>

[sa]
aws_access_key_id = <key>
aws_secret_access_key = <secret>
aws_session_token = <token>

[jmery]

@awschristou Figures ... seconds after posting, VS Code updated to 1.37.0. It appears that there was something cached between VS Code restarts which was resolved when it updated. Issue #705 seems to support this.

[awschristou]

Thank you for the confirmation @jmery

• Credentials caching is too aggressive #705 indeed will track overly aggressive caching of credentials (which requires restarting VS Code to flush)
• I've created Support upper case keys in the shared credentials file #732 to track supporting upper case keys (and made a reference to this issue)

I will close this issue, as the work will be tracked in these separate issues.

[eugenevd]

For what it's worth, I've just had the same error as the OP

$ code --version
1.51.1
e5a624b788d92b8d34d1392e4c4d9789406efe8f
x64
$ aws --version
aws-cli/1.18.180 Python/3.6.9 Linux/5.4.0-53-generic botocore/1.19.20

AWS Toolkit 1.15.0

What solved the problem for me was to change the profile entries in ~/.aws/config from
[profileX]
to
[profile profileX]

[VINAYREDDY26]

I am not sure about command error. Can you guys help me out.

[Tsdjimmy]

I am not sure about command error. Can you guys help me out.

Do this instead If you have homebrew you can install awscli like this:

brew update
brew install awscli

And then use the following to configure your aws with you access id and token:

aws configure

[KurtWAndrews]

I'm getting the following error which seems to be covered by this thread, but I can't see anything wrong with my aws config or credentials and aws cli is working fine.

• log file

2022-04-13 15:34:35 [ERROR]: log level: info<br>
2022-04-13 15:34:36 [INFO]: Retrieving AWS endpoint data
2022-04-13 15:34:36 [INFO]: OS:  Darwin x64 20.6.0
2022-04-13 15:34:36 [INFO]: Visual Studio Code Extension Host Version:  1.60.0
2022-04-13 15:34:36 [INFO]: AWS Toolkit Version:  1.37.0
2022-04-13 15:34:40 [ERROR]: login: failed to connect with "profile:default": Profile default could not be found or parsed in shared credentials file.
2022-04-13 15:39:37 [INFO]: telemetry: sent batch (size=9)
2022-04-13 15:39:44 [ERROR]: Profile default is not a valid Credential Profile: Profile default is not supported by the Toolkit.
2022-04-13 15:39:44 [WARN]: Shared Credentials Profile default is not valid. It will not be used by the toolkit.
2022-04-13 15:39:46 [ERROR]: login: failed to connect with "profile:profile default": Profile profile default could not be found or parsed in shared credentials file.
2022-04-13 15:41:30 [ERROR]: login: failed to connect with "profile:default": Profile default could not be found or parsed in shared credentials file.
2022-04-13 15:43:58 [ERROR]: login: failed to connect with "profile:default": Profile default could not be found or parsed in shared credentials file.
2022-04-13 15:44:37 [INFO]: telemetry: sent batch (size=9)

• .aws/config

[default]
region = us-east-1
output = json
ca_bundle = /Users/cn174265/ZscalerRootCerts/ZscalerRootCertificate-2048-SHA256.crt

• .aws/credentials

[default]
AWS_ACCESS_KEY_ID=<key>
AWS_SECRET_ACCESS_KEY=<secret>
AWS_SESSION_TOKEN=<session>

[justinmk3]

• .aws/credentials

[default]
AWS_ACCESS_KEY_ID=<key>
AWS_SECRET_ACCESS_KEY=<secret>
AWS_SESSION_TOKEN=<session>

Try lowercase key names (though this should have been fixed by #2396 ) :

[default]
aws_access_key_id=<key>
aws_secret_access_key=<secret>
aws_session_token=<session>

[KurtWAndrews]

Thanks, I think that did it. I just have to make sure my cli still works.

…

On Wed, Apr 13, 2022, 6:08 PM Justin M. Keyes ***@***.***> wrote: - .aws/credentials [default]AWS_ACCESS_KEY_ID=<key>AWS_SECRET_ACCESS_KEY=<secret>AWS_SESSION_TOKEN=<session> Try lowercase key names (though this should have been fixed by #2396 <#2396> ) : [default]aws_access_key_id=<key>aws_secret_access_key=<secret>aws_session_token=<session> — Reply to this email directly, view it on GitHub <#720 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAPYBHSDXMIER5HU4DI5FBTVE5HX3ANCNFSM4IJBT2AQ> . You are receiving this because you commented.Message ID: ***@***.***>

[INValentin]

Had the same issue removing spaces made it work!
FROM
[default] aws_access_key_id = <key> ....
TO
[default] aws_access_key_id=<key> ....

[justinmk3]

FROM
[default] aws_access_key_id = <key> ....
TO
[default] aws_access_key_id=<key> ....

@INValentin I can't reproduce this issue, I tried:

[test-spaces]
aws_access_key_id = ...
aws_secret_access_key = ...

and was able to connect using the test-spaces profile in AWS Toolkit for VSCode, version 1.47.

What version of AWS Toolkit for VSCode are you using? Does the issue occur with AWS Toolkit if you add spaces again?

Note that [default] must be on its own line, like this:

[default]
aws_access_key_id = <key>