# Is there an effort to migrate off v1 of the AWS SDK for Go?

**URL:** <https://discuss.hashicorp.com/t/is-there-an-effort-to-migrate-off-v1-of-the-aws-sdk-for-go/48091>\
**Category:** AWS\
**Created:** [December 16, 2022, 11:41pm UTC](https://discuss.hashicorp.com/t/is-there-an-effort-to-migrate-off-v1-of-the-aws-sdk-for-go/48091 "2022-12-16T23:41:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcanseco](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/jcanseco/32/32655_2.png) [@jcanseco](https://discuss.hashicorp.com/u/jcanseco)\
**Post date:** [December 16, 2022, 11:41pm UTC](https://discuss.hashicorp.com/t/is-there-an-effort-to-migrate-off-v1-of-the-aws-sdk-for-go/48091/1 "2022-12-16T23:41:21Z")

</div>

Hello folks,

I see that [terraform-provider-aws](https://github.com/hashicorp/terraform-provider-aws/blob/main/go.mod) depends on both [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go) and [github.com/aws/aws-sdk-go-v2](https://github.com/aws/aws-sdk-go).

Are there any efforts or future plans to migrate off of AWS SDK Go entirely in favor of using just AWS SDK Go v2?

We have a company policy where only one major version of a software project must be in use at any time, but exceptions can be granted if compliance is infeasible, so we’re looking to collect information on whether (and when) the AWS Terraform Provider will depend on only one major version of the AWS SDK Go.

Thanks.

---

<div class="post-metadata">

**Author:** ![jcanseco](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/jcanseco/32/32655_2.png) [@jcanseco](https://discuss.hashicorp.com/u/jcanseco)\
**Post date:** [January 10, 2023, 7:09am UTC](https://discuss.hashicorp.com/t/is-there-an-effort-to-migrate-off-v1-of-the-aws-sdk-for-go/48091/2 "2023-01-10T07:09:34Z")

</div>

Just a kindly ping on this
