Migrate configure-aws-credentials to use AWS SDK for JavaScript (v3)

[GeorgeDavis-TriumphTech]

Describe the feature

(node:1629) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)

Use Case

There is a warning message when we use aws-actions/configure-aws-credentials@v1-node16 in GitHub Actions workflow.

Proposed Solution

Migrate configure-aws-credentials to use AWS SDK for JavaScript (v3)

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

[rjminchuk]

seeing this as well

[povisenko]

+1
aws-actions/configure-aws-credentials@v1-node16

[ngb7h]

We're also using aws-actions/configure-aws-credentials@v1-node16, same warning.

[kellertk]

The JS v3 SDK no longer supports exporting a global credential object, which is used by our action. A major rewrite of the action and our tests is needed to support v3. This is in progress and will coincide with a v3 release of this action :)

[Haarolean]

It seems like they finally dropped the support for this after the deprecation.

Without any changes, it stopped working just in a matter of a few days, now we get this:

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
Error: Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers```

[mfn]

I can't (yet?) confirm any problems from my side, I'm using this action in 30+ workflows and they work; only the message is shown:

Run aws-actions/configure-aws-credentials@v2
  with:
    aws-access-key-id: ***
    aws-secret-access-key: ***
    aws-region: eu-central-1
    audience: sts.amazonaws.com
(node:2126) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)

This is from an hour ago.

[Haarolean]

@mfn hmm, thanks for double-checking I was convinced that it's related, I'll try to look into other things.

[AndrewReid-Journey]

It seems like they finally dropped the support for this after the deprecation.

Without any changes, it stopped working just in a matter of a few days, now we get this:

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
Error: Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers```

Interestingly, i'm having the exact same issue as you in some of my workflows now. Weirdly I have some workflows which still run OK (albeit showing the warning message about the maintenance mode plans for 2023) but others where this step is failing now. The only differences I can see between these workflows is that the failing ones are declared to run in a container where as the others are not. I wonder if this is the same scenario in your case?

[Haarolean]

@AndrewReid-Journey it turns out, on my end, it was related to a workflow being run on a branch from a fork. That's github's security measure which I forgot about. pull_request vs pull_request_target.

[LLBlumire]

I am having the same issue as @Haarolean

(node:1598) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
Error: Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers

Confusingly for me, I have never set up configure-aws-credentials before, and so assumed I must be doing something wrong, all online documentation for that error instructs to set id-token: "write", which I had already done.

This whole situation was very confusing, I suppose I picked a bad night to try and set up aws CD!

---

EDIT: nevermind, I had my configuration wrong! It's working for me now!