Awareness for end-of-support/EOL of AWS SDK v1 in indirect-require deps (update ref/switch to v2 before July 31, 2025)

[rgoltz]

Is your feature request related to a problem? Please describe.
According to this https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-go-v1-on-july-31-2025/, there will be no more releases for AWS SDK for Go v1 after July 2025. AWS as maintainer of this AWS SDK for Go package announced the EOL of the version 1 for July 31, 2025. After this date, there are no critical bug fixes and no security issues provided. Furthermore, the v1 SDK will not receive API updates for new or existing services, or be updated to support new regions.

Example for require-reference (there might be more):

mongodb_exporter/go.mod

Line 31 in f26ffbf

github.com/aws/aws-sdk-go v1.55.1 // indirect

Describe the solution you'd like
MongoDB exporter should consider identifying and updating modules/deps, which still using aws-sdk-go-v1. Once done, an update of this module and a new release should be provided (to enable also other projects, which using this project here). Such migration to AWS SDK for Go v2 - aws-sdk-go-v2 should reduce the technical dept and converges to use a single version of this SDK. There is a migration guide available: https://aws.github.io/aws-sdk-go-v2/docs/migrating/

[idoqo]

Hi @rgoltz , thanks for your report. We are aware of this and are tracking the upgrade to SDK v2 at https://perconadev.atlassian.net/browse/PBM-1468.

[github-actions]

This issue has been marked as stale because it has been open for 120 days without activity. Please remove the stale label or add a comment; otherwise, it will be closed in 7 days.

[rgoltz]

Hi @idoqo - Thanks for adjust the tag added by the bot.It seems that are still indirect deps using AWS SDK for Go v1. Hence, removing "stale" flag seems to be a good idea. 👍

[dehaansa]

I see that PBM has been updated to support AWS SDK v2, is anyone working to update the exporter to bring in the updated dependency?