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 :)!!!