Especially since they have bet so heavily on Docker which is built with golang.
I wonder if Amazon don't support golang directly because it's the Google language.
Source: I heavily contributed to boto in years past. It has progressed by leaps and bounds since then, but I still don't see it mentioned in the AWS blog posts when Ruby/Java/PHP get new shinies.
Boto has supported Python 3 since early August :)
After spending so much effort trying to get boto 3 to work with python 3 I completely gave up and re-wrote all my scripts in python 2. August isn't that far away.
Companies that provide programmable systems should be the first to provide SDK's, even for technologies not yet widely adopted. That goes for any company that provides something programmable.
Amazon appears to have no trouble at all justifying the massive development effort required for every new back end web service they build, but front end programming API access just isn't valued as much.
Honestly, is that really a surprise at all?
REST web services work well. Most languages have frameworks with excellent support for them.
Historically, the community has provided wrappers for popular APIs pretty quickly.
In the specific case of Go, it's still in early adopter territory. That means they are unlikely to have a problem using the raw APIs.
Their back end services make them money. Creating a Go API does not.
Makes it hard to justify investing development resources.
I did this in rough a week and a half of full-time work.
I'm more oriented that the language is new so is still hard to find devs without consider that is a very a big work port this huge amount of api.
For internal projects, situation is even worse and many of them are community-maintained.
Disclaimer: Amazon Employee.