I believe Google Cloud was launched after AWS so a head start helps for one.
AWS also has a free tier, it’s like giving the first hit of ecstasy to someone free. Why not use this free server. Then that server needs to expand and you make plans and youre hooked and know the AWS cloud better than Google.
Google Cloud offers a credit of $300 right now to try and get you involved but its not the same as a free tier of service. Once the $300 is gone its always going to cost you whereas you can downgrade a server back to the free tier if ya decide to do that.
There are also some wonky decisions that Google made that leave me annoyed almost daily. The fact you cant utilize smtp ports of the servers leaves me having to go all around to get a WordPress site to send emails…or the inability to easily transfer a project between accounts. I’ve landed myself in a situation where I transferred ownership but I didn’t remember to transfer billing but was no longer a project owner so I couldnt transfer billing anymore, customer service just acted like it made sense that I couldn’t use or config the resource but that my credit card was still going to be used.
SSH and SFTP into AWS fairly standardized and it is relatively seamless. Google makes these difficult.
The way they only give out one static ip address per zone. They have a BETA project and decide if its to allow multiple IPs but…what took so long? IP Aliases or multiple network ip addresses … on AWS I just added the IP addresses, why do I need more than one? Because my name servers need to have different IP address, but again I cant do it right now.
So with all these limits here and there I personally pay for my servers with AWS (its just easier to use) but I use Google Cloud for short experiments where I may need more than 1 IP, and a site that doesn’t ever send an email.is new and overdue.