Or what about Go? React?
Ok, some of these aren't proprietary, that if the big company supporting it would drop?
My point isn't to now learn AWS because everything else is proprietary. My point is that quite a few popular programming languages have corporate interests and can also give a bit of a vendor lock-in, to quite a degree.
C# for servers seems at the same point nowadays (and before you could still own software and hardware a lot more than today).
Go - problematic, but GCC has a compiler, which can bootstrap.
React - now, we are talking about the mess, the www is today, but technically you'll be able to compile webkit for years to come. And it has some big stakeholders.
AWS - everything is proprietary you can't "own" any tool at all. Amazon decides they don't want to do business with you - pooof. Your country decides to block AWS/USA blocks your country - pooof. Want to fix a bug - well, nothing you can do...
I think the bus factor for all of these technologies is not the same. Nor is the ease of switching. If AWS died tomorrow, people would switch to Google Cloud. If Facebook dropped React, it's insanely likely someone would come and take over (esp. since it's already open source).
The cost in switching technology is just too big for big libraries/big languages (e.g. even with Oracle somewhat dropping Java, it's still top 3 of must used languages).
The real skill of AWS is knowing the cheapest way to use it, not the easiest.
Maybe most people don’t need to know. But the truth is that a lot of these managed cloud services are wrappers/reimplementations around OSS tech or can be a massive overhead for your actual problem.
A great exercise to figure this out is to implement some of the cloud products as a toy project, targeted at your use case. You’ll quickly learn whats fluff and where the meat is.