Move to AWS SDK v2

[yaron2]

We're currently using the v1.x of the AWS Go SDK. v2 SDKs recently became stable and is recommended to migrate over.

[berndverst]

cc @robertojrojas

[robertojrojas]

@berndverst I'm planning to work on this for v1.11.

[joebowbeer]

@yaron2 end-of-support for AWS SDK for Go (v1) is effective July 31, 2025

https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-go-v1-on-july-31-2025/

[yaron2]

@yaron2 end-of-support for AWS SDK for Go (v1) is effective July 31, 2025

https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-go-v1-on-july-31-2025/

Thanks that's good info

[passuied]

@yaron2 I've started playing with Cursor to see if it helps with the upgrade... So far it seems to de a decent job... Should I go all the way? Would be good to have it out for 1.16... Or is someone already working on this on your side?

[yaron2]

@yaron2 I've started playing with Cursor to see if it helps with the upgrade... So far it seems to de a decent job... Should I go all the way? Would be good to have it out for 1.16... Or is someone already working on this on your side?

It'd be great if you can open a PR for this

[mikeee]

@passuied I've migrated sqs/sns with the common auth but won't have time blocked out for a little while. Feel free to open a PR and I'm happy to defer to you 🙂

[passuied]

I'm using it as a way to gauge how good cursor is... (it should be in theory for these mindless updates...). Let me see how far I can get in between meetings... :)

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.