Yeah, I've noticed that too
I've been an IT Infrastructure guy my entire nearly two-decade career. (Started out with tech support for LAN gear, shifted to 13 years in tech support for SAN gear, and now I'm a DR solutions architect.)
On a lark, I took a cheap AWS Architect course, and it totally dawned on me: My entire profession, IT infrastructure, is toast. Kaput. Kablooie. There are few reasons for anybody setting up a new IT shop to use the sort of environment I've spent nearly a couple of decades becoming a fairly well-paid expert on. The flexibility and ease-of-use the cloud provides means nobody has to pay somebody like me to make it all work. I'm really good at SAN design, remote mirroring, nitty-gritty protocol gnarliness, etc., and now there's no need for any of it.
And yes, it terrifies me. At this point, I'm learning as much as I can about cloud architecture as fast as I can, but I fear it may not be enough. (As in, I'll be able to find a new line of work, but it certainly won't pay as well as what I'm doing now, because I won't have the experience levels I have now on the new stuff.)
Now I know what the proverbial buggy-whip makers felt like.