AWS is easier to set up than to plan your own data center. The difference is that people who opt for AWS think they no longer need ops, and don't even have knowledge of networking. You still should have at least one network engineer to plan VPC and subnet layout.

As for GCP, I think it seems easier, because by default it uses public IPs for each instance. That doesn't necessarily mean that one you set up an instance and it runs, you did it correctly.

One nice thing though is that Google uses SDN for their internal networking and that made some things easier. Particularly seamless communication with other regions.

Azure is horribly complex too. There is an involuntary comical course on pluralsight [1] trying to explain all the different types of services and the small subtleties between services that do about the same thing, but not exactly the same. It’s hard not to leave even more confused.

[1] https://app.pluralsight.com/library/courses/microsoft-azure-...

I've looked into a few AWS service over the last week and coming from Azure I am very confused. It's not at all clear how AWS service are grouped together or why certain resources where created at all.

The resource group concept in Azure is, in my opinion, much easier to use and understand that VPCs in AWS.