✨ Migrate Node packages to AWS SDK v2

[LiangquanLi930]

What type of PR is this?
Add one of the following kinds:
/kind feature
/kind cleanup

What this PR does / why we need it:

• Migrates node package to AWS SDK V2.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #5402

Special notes for your reviewer:

Checklist:

• squashed commits
• includes documentation
• includes emoji in title
• adds unit tests
• adds or updates e2e tests

Release note:

Migrate Node packages to AWS SDK v2

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign nrb for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @LiangquanLi930!

It looks like this is your first PR to kubernetes-sigs/cluster-api-provider-aws 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api-provider-aws has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @LiangquanLi930. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[damdo]

/ok-to-test

[LiangquanLi930]

@damdo Hi, I have a question I'd like to ask — regarding

cluster-api-provider-aws/pkg/cloud/interfaces.go

Lines 33 to 38 in 701052c

	// Session represents an AWS session.
	type Session interface {
	Session() awsclient.ConfigProvider
	SessionV2() awsv2.Config
	ServiceLimiter(service string) *throttle.ServiceLimiter
	}

, should it be updated to

Session() awsv2.Config

as part of this issue we’re trying to address?

[k8s-ci-robot]

@LiangquanLi930: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-provider-aws-e2e-blocking	361c2f9	link	true	/test pull-cluster-api-provider-aws-e2e-blocking
pull-cluster-api-provider-aws-build-docker	361c2f9	link	true	/test pull-cluster-api-provider-aws-build-docker
pull-cluster-api-provider-aws-build	361c2f9	link	true	/test pull-cluster-api-provider-aws-build
pull-cluster-api-provider-aws-test	361c2f9	link	true	/test pull-cluster-api-provider-aws-test
pull-cluster-api-provider-aws-verify	361c2f9	link	true	/test pull-cluster-api-provider-aws-verify

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[damdo]

Hey @LiangquanLi930 I don't think so, but better to ask @punkwalker

[LiangquanLi930]

I saw #5521 — maybe we should wait for this PR to merge before proceeding with ours.

[damdo]

Yeah, that's probably better, let's pause this until we get the other in, thanks @LiangquanLi930

[punkwalker]

@LiangquanLi930 @damdo The session() can only be removed if all the dependent clients are migrated to SDK V2. Let’s wait for #5521 to merge and then cleanup every reference to SDK v1 sessions.