https://pulumi.com logo
Title
m

modern-school-54566

01/04/2023, 11:48 AM
Hello everyone I'm having an issue with my pulumi aws credentials it was working yesterday but 4 some reason 2day it refuses to confirm my aws credentials I have created new I am roles Reconfigured it with my aws cli Added It to my pulumi.stack.yaml as config values I even edited them from my .aws.config and .credentials directory in my root user But it still throws a invalid aws credentials wen I run pulumi up
r

rough-morning-53309

01/04/2023, 2:56 PM
Are your credentials validating successfully with the AWS CLI via
aws sts get-caller-identity
? Do you use a token as part of your credentials that has expired since yesterday? If using profiles, does the profile match in your config files?
m

modern-school-54566

01/04/2023, 3:02 PM
No tokens The aws credentials are failing I noticed this a while ago And I have only a default profile
r

rough-morning-53309

01/04/2023, 3:03 PM
aws sts get-caller-identity
--> is this failing as well?
m

modern-school-54566

01/04/2023, 3:08 PM
Invalid client token I'd Security token included in request not valid
I emptied my config and credential file created a new Iam user security credentials then configured them b4 trying aws St's get-caller-identity
r

rough-morning-53309

01/04/2023, 3:14 PM
It sounds like you might have some lingering AWS credentials in your environment that have an invalid/expired token. A few things you can try: • Check your exports for AWS creds • Open a new shell • Re-configure the AWS CLI with
aws configure
There are a multiple places that AWS creds can live, so you'll need to run through those and get a functioning
aws sts get-caller-identity
response in order to proceed.
m

modern-school-54566

01/04/2023, 3:18 PM
Thanks I'll get on it