Or better yet, rewrite it in Go to avoid both the fat blob and python dependency management at the same time!

Or put the API definitions into some database (sqlite, datascript + nodejs or babashka or nbb), then you can decide what http library or mocked http solution would you like to use, eg https://github.com/oliyh/martian

Most of the code is just a thin veneer over that information...

i mean, the go binary would still probably be a bit large, but having a statically linked binary to copy around would be welcome.

Touché!

I’ve been on both sides of this and some consumers are fine but some have no idea how to consume or initial setup is so broken, this is much easier

Right, no doubt that some customers required fully packaged solutions.

I guess it's generally hard to find the right balance, if you're catering to customers of different level of technical expertise/maturity.

(Btw, the previous comment was in reference to: https://github.com/aws/aws-cli/issues/4947)

aws cli v2 is such a sad story long live awscli1!