Peter Woodworth

I don't think this issue is related to the fingerprints issue, this error would occur before it gets a chance to send the request to the IDP if it's coming...

We now implement a retry behavior when the `getIDToken` call fails in `v3`, so please let me know if upgrading to `v3` helps with this at all.

I've subscribed to the issue @lkeijmel created, so I'll be up to date if there's any update there. Otherwise, I think the retry behavior on the token in `v3` should...

Is this still an issue? And by that I mean, is it still required that you wipe your credentials from your environment variables to suit this use case?

Hey @steven-jiang-valtech, It looks like based on your previous comment, that your role-to-assume arn may be misconfigured. If you were having an issue with the partition I wouldn't expect the...

Great to hear @steven-jiang-valtech 🙂 If anyone else runs into the issue, please ping me

We have a couple related issues to this like #112, we will see what we can do about use cases like this. Thanks!

Closing due to staleness. Please reopen an issue if you would like this to remain on our radar, or submit a new PR with the requested changes. Thanks!

It appears the workflow code pasted, and the screenshot differ in terms of configuration. Is this being attempted with OIDC, or with regular AssumeRole?

This action shouldn't attempt to use OIDC if you have properly setup your inputs https://github.com/aws-actions/configure-aws-credentials#assuming-a-role