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

[rgoltz]

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): https://github.com/grafana/beyla/blob/9976a4d5e9dbfa80613e6e2b3dbd67dc68ec6299/go.mod#L81

Grafana Beyla 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/

[marctc]

Thanks for reporting!

I think in our case that dependency comes from the usage of go.opentelemetry.io/contrib/detectors/aws/ec2. so updating the collector would do the trick. Related issue: https://github.com/open-telemetry/opentelemetry-go-contrib/issues/6860

[mariomac]

@marctc in the case of Beyla, I think it would be a bit more complex: https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/31300#issuecomment-2793058360