Drop AWS SDK for Go v1 and upgrade to v2 before EOL/end-of-support at July 31, 2025 - Heroku X
- Dominant language
- Go
- Stars
- 55
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
### Problem
As far as I can see there is an indirect dependency for `github.com/aws/aws-sdk-go` (AWS SDK for Go **v1**) in Heroku X:
https://github.com/heroku/x/blob/7222ba98f4044a9f19974c3564746c4c4f9a378b/go.mod#L9
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.
### Proposal
Heroku X should consider migrating (or updating references modules) to [AWS SDK for Go v2](https://aws.github.io/aws-sdk-go-v2/docs/) - https://github.com/aws/aws-sdk-go-v2/ to reduce the technical dept and converges to use a single version of this SDK: `github.com/aws/aws-sdk-go-v2`
The migration guides https://aws.github.io/aws-sdk-go-v2/docs/migrating/ is a good starting place to understand what needs to be done.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with go.mod at the referenced dependency line and inspect the dependency graph to identify which Heroku X packages bring in AWS SDK for Go v1. Read the AWS SDK for Go v2 migration guide before tracing those references. Done means the v1 dependency is removed and Heroku X converges on github.com/aws/aws-sdk-go-v2 without breaking affected packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- backend, cloud
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100