4 ms·
> universal thinking within AWS is that people will ultimately use the API/CLI/SDK ( ͡° ͜ʖ ͡°) - But still 99% of tutorials and documentation refer to the UI.
by postit 7y ago
> universal thinking within AWS is that people will ultimately use the API/CLI/SDK
( ͡° ͜ʖ ͡°) - But still 99% of tutorials and documentation refer to the UI.
- lentil 7y agoTo be fair, the AWS documentation nearly always covers both.
- rolltiide 7y agoan outdated version of both. Here's a bunch of buttons! What do you mean you didn't install the CLI, discover your system has mixed up versions of the package manager, and finally get around to running this convoluted command, after you learn how to get a list of IDs from your organization with the CLI
- nostrebored 7y agoThe AWS cli is a simple pip install and the CLI documentation nearly universally includes samples. Input and output can be JSON. There are a lot of legitimate complaints about AWS but the CLI is pretty decent.
- rolltiide 7y agoIt has a steep learning curve. Every time something new roles out and AWS doesn't have a button for that one thing, your static site trying to follow the best practices now needs to know this and have python package managers installed and updated. I would say it is a legitimate complaint, it is a horrible user experience amongst people who aren't even considering what other people would think of it.
- jasonlotito 7y ago> It has a steep learning curve. I mean, I guess if you are new to AWS entirely. I find the documentation for most things accessible and easy. For the things I want more information on or I'm not clear, support is fairly quick to help and point to the documentation. Most of the time it's the documentation I skipped because I assumed I knew it.