Had a similar experience with GCP -- wanted to run an experiment in AWS, Azure, and GCP side-by-side. AWS and Azure were set up within a day. GCP required hitting up support to "turn on the feature," then a salesperson called to tried to upsell over a few calls before they'd turn it on. There was then confusing payment UI flow that meant my payment wasn't set up correctly. Overall took 3 weeks of back and forth to even start. This was 4 years ago, so maybe it's changed a bit now, but it's hard imagining depending on them as a business unless you're the scale of Snap and have leverage.
I'm reading this comment and this thread, thinking of the excellent service we get from AWS (which we pay for) and that stuff just works, and wondering why on earth anyone would risk their business on a Google service.
AWS has its own serious liabilities - particularly the issue with a lack of billing caps, and the resulting surprise bills. It's discussed here pretty regularly. That may not be unique to AWS, but my point is it's hard to avoid serious liabilities as a small account on any of these clouds.
