This message was deleted.

sparse-intern-71089

01/04/2023, 11:48 AM

This message was deleted.

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?

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

rough-morning-53309

01/04/2023, 3:03 PM

aws sts get-caller-identity

--> is this failing as well?

modern-school-54566

01/04/2023, 3:08 PM

Invalid client token I'd Security token included in request not valid

modern-school-54566

01/04/2023, 3:10 PM

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

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.

rough-morning-53309

01/04/2023, 3:15 PM

Additional reference

modern-school-54566

01/04/2023, 3:18 PM

Thanks I'll get on it

👍 1

2 Views

Open in Slack

Previous Next

Pulumi Community

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.