Azure and AWS are more than just VMs. Containers and container orchestrators (and microservices architecture you can create with it) is very different from traditional hypervisors and VMs in the sense of scalability, and creating/destroying containers really quickly on an as-needed basis ("elasticity"). There's also caching, lots of APIs you won't get with a basic hypervisor, and the fact that many places are looking to hire people with these specific skills. And, of course, the issue of not having to build a data center to have at-scale resources.
A reductionist approach to it isn't going to make anyone think you're smart just because you're vaguely familiar with something you think is the same even when it's really not.
Documentation is important, but you're right, a lot of documentation is hard to follow. I think part of that is because experiential learning is best. It's hard to get an idea of how to use something based on a man page, but doing on online course, or an in-person workshop at a hackathon is wonderful for learning. These days, I actually prefer watching Youtube tutorials over reading documentation, with the one exception being the Oracle API documentation, which is really good, even if you're not a fan of Java.
But I also think a lot of boomers in tech take pride in the fact that there is a barrier to entry, and they kind of enjoy that some things are difficult to learn, even if it's only because documentation and community resources are poor. They want that elitist mentality instead of making things easier to use.
A program being hard to use is an example of bad UX, which is the fault of the developer. But a lot of "1337" people think something being hard to use makes it better. I do a lot of frontend development and if the user can't figure out how to use it, that's your problem, not theirs.