No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

our team is running python packages
```pulumi = "&gt;=1.10.1"
pulumi-aws = "&gt;=1.0.0"```
with pulumi version 1.10.1.
pulumi is reporting that it cannot find aws credentials:
``` -  aws:ebs:Volume prometheus_volume **deleting failed** error: unable to discover AWS AccessKeyID and/or SecretAccessKey - see <https://pulumi.io/install/aws.html> for details on configuration
    pulumi:pulumi:Stack prometheus-dev running error: update failed
    pulumi:pulumi:Stack prometheus-dev **failed** 1 error
 
Diagnostics:
  aws:ebs:Volume (prometheus_volume):
    error: unable to discover AWS AccessKeyID and/or SecretAccessKey - see <https://pulumi.io/install/aws.html> for details on configuration
 
  pulumi:pulumi:Stack (prometheus-dev):
    error: update failed```
but the command `aws --profile=&lt;profile name&gt; ec2 describe-instances` works as expected. `&lt;profile name&gt;` from the preceding command is also configured in the application's Pulumi.dev.yaml

I tend to think this is a case of user error. Is there some combination of package versions that I should be using to avoid this behavior?

additionally, our team recently changed our convention surrounding aws profile names. Is it possible that pulumi is trying to use old names that are cached somewhere?