-
Notifications
You must be signed in to change notification settings - Fork 464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UnrecognizedClientException: The security token included in the request is invalid. #788
Comments
Getting
I'm using aws-actions/configure-aws-credentials@v2 |
What happens when you run
|
Similar issue here where a subsequent workflow step fails with this error. Might be a coincidence, but if we can't find anything wrong with anyone's configurations there may be something up |
aws sts get-caller-identity works fine , displays the role assumed and for checkig when I add
It displays the bucket , It assumes the right role and list the buckets. |
Upgraded to v3 fixed this issue for me |
Glad to hear that the v3 upgrade helped @minh-gfg. @gayatribrg have you tried upgrading to v3? We launched it yesterday. If you're still running into issues after v3, based on the information you've provided it wouldn't seem like it was due to this action since it appears your runner is properly assuming the role |
Tried v3 , it promptly shows the role assumed. Despite that, when I call this action peterkimzz/aws-ssm-send-command@master, |
Unfortunately it looks like peterkimzz/aws-ssm-send-command hasn't been updated (that is, the dist files) in about 3 years. I'm not sure how code this old would interact with the AWS_SESSION_TOKEN, but if you're using temporary AWS credentials you actually have 3 env variables to worry about, the ACCESS_KEY_ID, the SECRET_ACCESS_KEY, and the SESSION_TOKEN. If the action can't handle the session token, you'll get this error. I'd also point out that this action is fairly trivial, if you look at the source. It takes your inputs and directly passes them to an SDK call. Since they're using a version of the AWS JS SDK that's soon to be deprecated, and it doesn't look like the author is updating the repo anymore, I'd recommend you construct an SSM call yourself instead of relying on the aws-ssm-send-command action. Closing this issue as can't repro. |
Comments on closed issues are hard for our team to see. |
Describe the bug
I am using aws-actions/configure-aws-credentials@v2 to assume a role and I realize the temporary credentials generated as part of env can be used in the next step.
However on step 2 I get the error "UnrecognizedClientException: The security token included in the request is invalid.
code: 'UnrecognizedClientException'"
Expected Behavior
Tempoarary credentials should be successfully used in next steps.
Current Behavior
I get the error "UnrecognizedClientException: The security token included in the request is invalid.
code: 'UnrecognizedClientException'"
Reproduction Steps
Call both these actions and kindly let me know what is being missed.
Possible Solution
No response
Additional Information/Context
No response
The text was updated successfully, but these errors were encountered: