Yeah if they were at least offering some added benefit, like guarantees of correctness, more detailed explanations, etc., then I could see it.
But otherwise it seems more like an insult.
But otherwise it seems more like an insult.
Yeah, no. I have to strongly disagree with this.
AWS's documentation about operating AWSs products and services I assume are correct and accurate.
If I follow their guides and end up breaking something because it turns out they forgot to tell me about something important, I would consider that a breach of warranty.
The only reason I can think of where documentation should be behind a pay/auth-wall is if it was generated specifically for your circumstances as part of some kind of solutions architecture or technical support process.
That’s exactly what this is, actually. These aren’t the AWS docs. The linked site is the AWS support forums in which AWS employees, AWS support and/or other known contributors from the AWS community will give you personalized responses to questions you have.
Some of these questions are more generic, and so aren’t personalized, but they’re still the result of a question-and-answer on the forum.
I disagree that these are specific enough to warrant being private. I'm thinking more along the lines of your very specific resources/application/architecture.
This is more like a curated version of Stack Overflow.