This is literally my area of expertise.
Factually very incorrect. In point of fact, there has been a massive consolidation of infrastructure expertise and devs deploying straight to production. There has been a massive reduction in building QA, testing and staging environments, and a dramatic reduction in associated staffing.
Production systems administrators have all but been run out of the industry because they're not sexy and they say "no" to new shinies in the name of stability.
See below:
For what?
Why not?
I'm a cloud systems architect with more than 30 years of systems, security, scalability and reliability expertise. Former projects include building a cloud backend for the release of a mobile operating system called WebOS that was launched for millions of users on the Palm Pre platform, scaling and automating said platform to create "Cloud 2.0," an enterprise-level PaaS/SaaS/IaaS modular compute cloud for Hewlett Packard. See also: principal systems architect for the nation's first large scale DSL ISP with customer-installed CPE, Microsoft WebTV, Oracle, eBay/Paypal, and so many more. Currently my side gig involves doing multi-cloud architecture for several clients, including DR, gitops, kubernetes, and so on.
I'm not anti-cloud.
Putting duct tape over holes is not fixing a problem. There are major systemic issues that need to be addressed. I expect at some point in the next 3-5 years there will be a multi-cloud outage that significantly impacts the world economy.
This is not a security issue*, but I agree.
... ?
Completely agree that this is a contributing factor.
All of the secondary and tertiary effects at play here are avoidable, unforced errors on the part of the companies that use these services.
This stuff is hard, but when expertise is ignored in favor of the bottom line, this is the natural consequence.