In order to understand the difference between Google VPC and AWS VPC, let’s take the following scenario.

You have created a healthcare application and have setup a Big data infrastructure in US region (for consuming public healthcare data sources/documents). Later. you want to deploy the application to UK region and have setup servers in UK region (for regulatory requirements) to host consumer data in UK region only. However, as part of the UK application, you want consume the vast amount of public data directly from Big data servers hosted in US region.

To implement the above scenario in AWS, you would need to create two VPC, one in US region and one in UK region, ensure the ip address doesn’t overlap and setup and approve VPC peering between the two VPCs.

On the other head, Google VPC is designed as a global construct, where a single Google Cloud VPC can span multiple regions and uses the google internal network (without going through the internet) for communication. So you have less infrastructure overhead to manage with Google VPC.