Peter Woodworth

Fixed by #739, this is now included on `v2.2.0`, and as such `v2`. Thanks @dimitar-hristov for your contribution!

This should be fixed in `v3`, let me know if it's not

@newfunda Have you created an identity provider in your AWS account? See [here](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services#adding-the-identity-provider-to-aws)

This should be fixed in `v3`, thanks for the patience everyone

There's now an example of this in the docs

I'm going to be closing this because we've decided we will not support it. If you need to configure the latest CLI for any reason, you can do that through...

It looks like this issue has been resolved, as I can't find any documentation stating the aud is anything other than `sts.amazonaws.com`, and this issue hasn't had activity in a...

A combination of `role-chaining` or the newly introduced [`unset-current-credentials`](https://github.com/aws-actions/configure-aws-credentials#unset-current-credentials) in `v3` may help in some cases where this action runs multiple times

> The only way to work around is to using boto3, read the deployed stack (describe) and looking for the outputs given exported names. When you need to make an...

Feel free to open another issue/discussion if you are still experiencing this. Thanks!