Upgrade AWS SDK for Go from v1 to v2

[harrisgugu]

The node-problem-detector is currently utilizing a version of the github.com/aws/aws-sdk-go that is approaching its end-of-life. According to the official AWS announcement, AWS SDK for Go v1 will reach its end-of-support on July 31, 2025.[1][2][3] After this date, it will no longer receive updates, including critical bug fixes and security patches.[1][2][4]
A customer's vulnerability scanner has flagged the following dependency in /home/kubernetes/bin/node-problem-detector as an EOL version:
pkg:go/github.com/aws/aws-sdk-go(1.44.72)

This is also reflected in the go.sum file on line 114:

github.com/aws/aws-sdk-go v1.44.72 h1:i7J5XT7pjBjtl1OrdIhiQHzsG89wkZCcM1HhyK++3DI=
github.com/aws/aws-sdk-go v1.44.72/go.mod h1:y4AeaBuwd2Lk+GepC1E9v0qOiTws0MIWAX4oIKwKHZo=

To ensure the security and stability of the node-problem-detector, it is crucial to migrate from the EOL AWS SDK for Go v1 to v2. AWS has provided a migration guide to facilitate this transition.
Please prioritize this upgrade to mitigate any potential risks associated with using an unsupported SDK.

[hakman]

AWS SDK for Go is an indirect dependency of the deprecated Stackdriver exporter. Any related risks should be minimal.

[hakman]

This should be addressed by #1141.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten