I'll trade you responsibilities. I work at a small agency and often do work for non-technical clients, or get hired to work on a completely unmaintained legacy

I'll trade you responsibilities. I work at a small agency and often do work for non-technical clients, or get hired to work on a completely unmaintained legacy system. I end up owning nearly everything myself, and it's a massive pain in the ass. You might be frustrated with the process of getting a new VM, but you also don't have to own and maintain all the VMs by yourself. I bet you won't have to personally manage the billing of this VM directly, or monitor for any changes in usage or pricing, etc, but somebody in your organization will. I often have to own and manage the SSL certs on dozens of unrelated properties... and own and address all the front end issues in every framework... and all the ci/cd issues for every legacy codebase... and anything else I want I gotta do. I also have to properly research all providers and price tiers and budget it all for my clients and then sell them on any service I consider worth it.