3 ms·
All of the AWS services I’ve used are difficult to work with. Documentation is often vague, outdated, incomplete, or nonexistent. The whole system seems designe
by grumple 6y ago
All of the AWS services I’ve used are difficult to work with. Documentation is often vague, outdated, incomplete, or nonexistent. The whole system seems designed to create jobs for AWS admins. Yes, you’ve got tons of power and control, but what we often want is transparency and simplicity, and that’s what AWS is worst at doing natively.
- recogepelotas 6y agoI disagree on the documentation bit. I think AWS's docs are really good overall. You have the services FAQs for high level overview + AWS Docs to get deep in to the weeds.
- pera 6y agoEvery time I have to read some AWS docs I get blinded by enterprise buzzwording and just want to run away...
- erikerikson 6y agoYou learn to avoid those pages. Besides, there are solid reference pages behind. I can't say the same for Azure.
- lostmyoldone 6y agoThey are good in some areas, but certainly not good in others. Eg when it comes to how aws codebuild/deploy and how ECS service/instance/task roles interact. It seems AWS teams are very vertical, leading to more complex cross services interaction being badly documented, as it's "nobody" who truly owns it?
- erikerikson 6y agoYes, their organizational structure and the lack of trust that sometimes flares up between teams really shows in the integration. Which is, of course, exactly the level where most customers live. IAM used to be exactly that but they centralized that cross-cutting concern and it's improved a lot.
- jrott 6y agoHonestly I’ve found most AWS services hard to work with because of IAM. Though I do agree with you about the docs.
- mobjack 6y agoMy issue is that most of the examples in the documentation either have or assume lax IAM policies.