@Liquidmantis I'm glad it helped! Thanks for adding additional context, I'm sure that'll help in future searches :)

Thank you! I had this same issue using the Terraform plugin and this fixed it for me

Adding the error for the search engines because it took me some experimenting to find this thread:
[ERROR] 2023/12/06 14:17:22 could not run plugin Terraform CLI: failed to provision credentials, encountered error(s):
source profile "default" does not exist in your AWS config file

jinux_go I'm glad it helped!

Hello andi_t_1P
I have experience the same issue and resolved it by following the kerren's method.

```
$ rm -rf ~/.aws
$ op plugin run --debug --cache=false -- aws ls s3
8:36PM | DEBUG | Session delegation enabled
8:36PM | DEBUG | NM request: NmRequestAccounts
8:36PM | DEBUG | NM response: Success
8:36PM | DEBUG | NM request: NmRequestAccounts
8:36PM | DEBUG | NM response: Success
[ERROR] 2023/10/25 20:37:00 could not run plugin AWS CLI: failed to provision credentials, encountered error(s):
source profile "default" does not exist in your AWS config file
$ cat ~/.aws/config # This prints nothing
$ echo '[default]' > ~/.aws/config
$ op plugin run --debug --cache=false -- aws s3 ls
8:39PM | DEBUG | Session delegation enabled
8:39PM | DEBUG | NM request: NmRequestAccounts
8:39PM | DEBUG | NM response: Success
8:39PM | DEBUG | NM request: NmRequestAccounts
8:39PM | DEBUG | NM response: Success
(... and the output from aws-cli follows)

```

1Password for Mac 8.10.18 (81018040)
aws-cli/2.13.17 Python/3.11.5 Darwin/22.6.0 source/arm64 prompt/off
macOS 13.6 Apple Silicon

Hi, andi_t_1P

I have experienced the same issue and resolved it by following the kerren's method


$ rm -rf ~/.aws/config
$ op plugin run --debug --cache=false -- aws ls s3
8:36PM | DEBUG | Session delegation enabled
8:36PM | DEBUG | NM request: NmRequestAccounts
8:36PM | DEBUG | NM response: Success
8:36PM | DEBUG | NM request: NmRequestAccounts
8:36PM | DEBUG | NM response: Success
[ERROR] 2023/10/25 20:37:00 could not run plugin AWS CLI: failed to provision credentials, encountered error(s):
source profile "default" does not exist in your AWS config file
$ ls ~/.aws
config
$ cat ~/.aws/config # This prints nothing
$ op plugin run --debug --cache=false -- aws s3 ls
8:39PM | DEBUG | Session delegation enabled
8:39PM | DEBUG | NM request: NmRequestAccounts
8:39PM | DEBUG | NM response: Success
8:39PM | DEBUG | NM request: NmRequestAccounts
8:39PM | DEBUG | NM response: Success
(... and the output from aws cli follows)


1Password for Mac 8.10.18 (81018040)
aws-cli/2.13.17 Python/3.11.5 Darwin/22.6.0 source/arm64 prompt/off
macOS 13.6 (Apple Silicon)

And for anyone else landing here that wants to understand the .aws/config file, have a look at https://catalog.us-east-1.prod.workshops.aws/workshops/79521eff-62b5-4792-a2e0-6dbb59d83f4a/en-US/20-configuration/profiles#:%7E:text=AWS%20Config%20Profiles&text=The%20default%20profile%20name%20is,setting%20the%20AWS_PROFILE%20environment%20variable. for details.

Hi andi_t_1P thank you very much for your response :) I was able to resolve it with your help, however, I think it may still need to be a bug/issue raised because it doesn't seem like expected behaviour.

Originally, I didn't have anything in the .aws/config file:

```
$ cat .aws/config

~
$ aws s3 ls
[ERROR] 2023/08/01 19:46:59 could not run plugin AWS CLI: failed to provision credentials, encountered error(s):
source profile "default" does not exist in your AWS config file

```

As far as I understand, you don't necessarily need the .aws/config file for things to function?

Anyways, I then made a [default] entry to see if that would help:

```
$ cat .aws/config
[default]

~
$ aws s3 ls

Output!!

...

```

So it seems that there is a requirement for the .aws/config file to exist and for the [default] line to be there, even if there is nothing underneath it. It's probably not the worst thing to expect that so that people know what their defaults are, but I do think then https://developer.1password.com/docs/cli/shell-plugins/aws/ would need to be altered to include the [default] entry in the .aws/config file as a prerequisite?

Either way, andi_t_1P thank you very much for the help, I'm super happy I'm able to use this again :)!!!

Hi kerren! It seems like profile default cannot be found in your .aws/config file. Is your use case not dependent at all on the .aws/config file? In that case, I'd call this a bug and I'll file an issue internally. Is you .aws/config file present at all? If yes, what does it look like?

Best,
Andi

Hi all, is anyone else experiencing this issue? I've updated all software and I'm still experiencing this issue:


[ERROR] 2023/07/31 15:36:00 could not run plugin AWS CLI: failed to provision credentials, encountered error(s):
source profile "default" does not exist in your AWS config file