I'm not saying I entirely disagree. I'm mostly suggesting that moving toward systems like Kubernetes and Terraform help you to reduce lock-in so that you can pick the best tool for the job. 7 years ago, it made sense to use AWS and not look back. But I'm sitting here now, and a lot of software in our stack is pretty tied to AWS when I'd much rather use GCP.

The furniture analogy is a bit flawed. I can get comfortable in a new, furnished house, but furnishings don't come with vendor lock-in. Cloud services naturally do, at least the highly proprietary ones. I'm not saying put the furniture in the basement, I'm just saying throw a slipcover over it so we don't touch it directly. :)

DigitalOcean meanwhile is a lot more limited. The new stuff they've added is nice with firewalls and load balancers, but the tooling with AWS is more complete and I can utilize a fair bit of that tooling from within Kubernetes, including things like Amazon's certificate provisioning.

Basically to be clear, I'm saying maybe now embracing GCP and Azure seems like a solid plan, but years down the road you might want to have some more mobility. If you're already using things you can bring with you to the next provider, you're going to be ahead of the curve.