signature expired error
moba1 opened this issue · comments
- I am using the latest release of AWS Vault
- I have provided my
.aws/config(redacted if necessary) - I have provided the debug output using
aws-vault --debug(redacted if necessary)
I got following errors when running aws-vault exec <profile> -- aws s3 ls on WSL.
aws-vault: error: exec: Failed to get credentials for <profile>: operation error STS: GetSessionToken, https response error StatusCode: 403, RequestID: xxx-yyy-zzz-www-xxx, api error SignatureDoesNotMatch: Signature expired: 20221005T132736Z is now earlier than 20221006T041807Z (20221006T043307Z - 15 min.)
Since I use pass as backend, I tried to remove profile with aws-vault remove and initialize pass.
But, aws-vault outposts aforementioned error and I cannot run command with aws-vault.
Here is what aws-vault --debug option.
2022/10/05 22:35:49 aws-vault v6.5.0
2022/10/05 22:35:49 Loading config file /home/xxx/.aws/config
2022/10/05 22:35:49 Parsing config file /home/xxx/.aws/config
2022/10/05 22:35:49 [keyring] Considering backends: [pass]
2022/10/05 22:35:49 Using a session duration of "15m0s" from AWS_SESSION_TOKEN_TTL
2022/10/05 22:35:49 Profile 'default' missing in config file
2022/10/05 22:35:49 profile <profile>: using stored credentials
2022/10/05 22:35:49 profile <profile>: using GetSessionToken (with MFA)
Enter MFA code for arn:aws:iam::<account id>:mfa/<IAM user name>: <MFA code>
2022/10/05 22:36:00 Looking up keyring for '<profile>'
aws-vault: error: exec: Failed to get credentials for <profile>: operation error STS: GetSessionToken, https response error StatusCode: 403, RequestID: xxx-yyy-www-zzz-xxx, api error SignatureDoesNotMatch: Signature expired: 20221005T133600Z is now earlier than 20221006T042553Z (20221006T044053Z - 15 min.)
Sorry, my wsl environment time was off.