To avoid using long-term AWS credentials, please update your workflows to authenticate using OpenID Connect. about configure-aws-credentials

[Ga13Ou]

Hi @mattpopa thanks for reaching out. We removed that warning here: #926. I couldn't reproduce the warning when testing but I may be missing some steps, are there any other details you can share regarding this?

Any visibility on when this will be added to v4 ?

[tim-finnigan]

Thanks for following up - just released 4.0.2 and pointed v4 to include latest changes, so the warning should now be removed: https://github.com/aws-actions/configure-aws-credentials/releases.

[tim-finnigan]

Hi @mattpopa thanks for reaching out. We removed that warning here: #926. I couldn't reproduce the warning when testing but I may be missing some steps, are there any other details you can share regarding this?

[mattpopa]

Hi @mattpopa thanks for reaching out. We removed that warning here: #926. I couldn't reproduce the warning when testing but I may be missing some steps, are there any other details you can share regarding this?

Thanks for replying. I don't see that change inside v4

git tag --contains 6129f329e60ccdcc69cae650f925172621807647

Let us know if there's a plan to update v4 to include that change.

[ponkio-o]

Hi, I'm facing the same issue. It looks reverted on the following PR.
#871

Our environment are using sts:AssumeRole (without long-term credentials), but showing the warning.

[ponkio-o]

@tim-finnigan Hi, I checked the v4.0.2 that doesn't showing the warning when I use sts:AssumeRole (without IAM access key) on self-hosted runner.

[github-actions]

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.