I'm always extra-skeptical about devs who choose to use click-baity titles to explain why a widely used piece infrastructure is useless. The merits and demerits

I'm always extra-skeptical about devs who choose to use click-baity titles to explain why a widely used piece infrastructure is useless. The merits and demerits of AWS have been discussed in depth by folks with way more experience and knowledge than this author, and in most cases "Never Use Amazon" would be found as a laughable conclusion. Nevertheless, I hope AWS reads this to get an idea about how they still need to improve their accessibility and image as a company overall. It's completely true that the transparency and accuracy of the "status page" is terrible because no product team wants to admit something went wrong. It's also true that their Premium Support is constantly overwhelmed and often not incredibly useful but still essential for many cases (This basically boils down to them having huge turnover rate, a low number of people who actually have skills to do the high-level support, and having too many ways to "game" the system where customers who spend nearly nothing get away with taking way too much support time and substituting paying actual architects with constant support cases. Increasing cost of support would actually be the best move here.) Regardless, this plays into the narrative that I've always observed. AWS, despite being easy to get going with, is also incredibly easy to mess up. The fact that there is a certification system spanning so many different parts of AWS should go to show the disconnect between how much AWS actually expects you to master before using it, and how much the average dev really wants to learn before jumping in (reading a blog post is not gonna cut it.)