This message was deleted.
# general
s
This message was deleted.
r
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
No tokens The aws credentials are failing I noticed this a while ago And I have only a default profile
r
aws sts get-caller-identity
--> is this failing as well?
m
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
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
Thanks I'll get on it
👍 1