Idea #10477
Updated by Tom Clegg about 6 years ago
Choices include * Switch to official AWS Go SDK, https://github.com/aws/aws-sdk-go. SDK. Kubernetes made the switch in May 2015. "The 2015, so probably safe for us too. https://github.com/kubernetes/kubernetes/pull/8297 The Kubernetes PR":https://github.com/kubernetes/kubernetes/pull/8297 PR also provides insight into what needs to be changed and possible approaches to migrating the code. * new/upcoming v2 of official AWS Go SDK, https://github.com/aws/aws-sdk-go-v2 * minio-go, client library from S3-compatible cloud storage system: "godoc":https://godoc.org/github.com/minio/minio-go / "API docs":https://docs.minio.io/docs/golang-client-api-reference.html ... This might have better compatibility with non-Amazon S3 services like Google cloud storage. While we will probably choose the official client library when we add Go code that uses EC2, that doesn't necessarily qualify as a reason to choose the official library for storage as well.