A very awkward to use version two SDK by Amazon Web Services

Published: Wednesday, Aug 18, 2021 Last modified: Sunday, Jun 9, 2024

AWS logo Go logo

Yesterday I introduced my colleague to aws-sdk-go-v2 and I must say it was one of the most frustrating experiences of my life!

tl;dr I don’t recommend aws-sdk-go-v2 despite shilling it in

the IDE experience

VScode with Copilot actually is a hindrance because most Golang/AWS code is written for version one of the AWS GO SDK. It keeps suggesting code that will not work with!

If you are new to an API, you are relying on the IDE discover types and such in order to get work done. VScode could not second guess I needed for example to able to roll up the log Groups I was pulling down. Incredibly frustrating. Furthermore EVEN IF I KNOW WHAT I AM DOING, VS code is always asking me to manually go get something? WHY MAKE ME JUMP HOOPS?

Furthermore, I don’t know why, may times it just couldn’t tell me information about structs I was interested in. Instead I had to use the broken experience of the API docs.

Searching the API docs developer experience is terrible

If you are careless you can easily search or follow a link and simple be looking at the WRONG API docs:, i.e. not version 2.

I somehow managed to use some weird fork for a while whilst developing.

If you use as I do, you will find Github’s search syntax seems to choke on hyphens and slashes.

The SDK is non-idiomatic

The use of pointers (string pointers, integer pointers, etc) all over the SDK really goes against how Golang is supposed to be written.

The API is generated and you can tell. No examples inline in the API docs. Lots of confusing paradigms like aws.String(“what the hell”).

Worst is in many cases, like for example adjusting Limit: aws.Int64(51) as opposed to the 50 API limit, will result in head scratching experiences like:

go nil pointer reference

The documentation is terrible

I generously gave more of my precious time to filing in this bug report about their broken developer guide.

I usually think of using aws-sdk-go-v2 because it has better cfg structures for complex credential handling. Fact is, it’s a nightmare. Such a shame since I advocate both AWS & GO.