[sdan]

I don't really consider either having superior UI... but AWS's endless list of services when you click for the dropdown is a bit too much to handle. Not to mention how you'll have to use their search bar to get to what you want.

One thing I do credit them on is SSHing into an instance is a lot easier than GCP's "gcloud" way (I say this since I recently found the "gcloud" sdk to take over 10g on my laptop) and even if you use SSH on GCP, they make it considerably harder than AWS (although somewhat more secure for beginners... to prevent from attackers to getting to port 22).

[maktouch]

You don't need to use gcloud to ssh. Just add your keys in your projects' Metadata, and you'll have ssh access to all servers.

Each member of your team can do it, and it works retroactively.

[sdan]

Yeah that does work (which I have managed to pull off)... but I feel like it's a bit more of a pain (very slightly) to change the metadata, open up the ports and whatnot to ssh. I think AWS just tells you to download a .pem file and ssh.

In conclusion, I guess both ways aren't bad. I just seem to prefer AWS here because for me it was a bit easier than GCP because I ran into several problems when sshing to GCP initially.

[tpmx]

So it was easier for you to use AWS initially because you were used to AWS. Gotcha. ;)