Meta note: All things considered, Amazon has it pretty good. They put out a barely usable, bare-bones, but fully functional tool in awscli. Paying customers of AWS have to perform the engineering effort to make the API more usable, and some even open-source their projects like this. AWS is an incredible business model.
My reasons for continuing include:
- I prefer to use command line over ClickOps
- Using Bash-My-AWS makes me more effective at work
- The emergent UX is equally applicable to other services (e.g. bash-my-github, bash-my-spotify)
- The intrinsic satisfaction from creating
- Helping improve the experience for others
I was able to write a simple command that returned all songs a friend and I had in common in our public playlists.
I forget the exact syntax but it was something roughly along the lines of:
$ sort <(
user-playlists alice | playlist-tracks
user-playlists bob | playlist-tracks
) | uniq --repeatedI love that a community has an option to build components and share the same. It has made my work much more productive.
But we certainly agree on that last point: it’s an incredible business model.
AWS CLI v2 previews were released in Nov 19 and while this may contain some breaking changes, I wouldn't be surprised if all the commands BMA uses continue to work as normal.
https://aws.amazon.com/blogs/developer/aws-cli-v2-installers...
Not to take anything away from the author of this project - Bash-my-aws looks fantastic - but it only helps you with a few core services. Same appears to be true of the commandeer tool that has also been mentioned in this thread. And the same is true for localstack, and on and on.
I really wish AWS would devote some resources to filling in these gaps themselves, and comprehensively.