VPC Peering (GCP)

Step 5 — VPC network peering

The transport transport
GCP Transport — a Network Connectivity resource created via `gcloud beta network-connectivity transports create`. Represents the GCP side of the cross-cloud interconnect link. creates a managed peering network. Peer your workload VPC VPC
Virtual Private Cloud — an isolated private network. Both AWS and GCP use VPCs. The interconnect peers the two VPCs for private routing. to it so routes flow to your GCE GCE
Google Compute Engine — GCP virtual machine instances. The demo GCE VM is reachable via IAP tunnel SSH. VM.

export PEERING_NETWORK="$(gcloud beta network-connectivity transports describe "$TRANSPORT_NAME" \
  --region="$GCP_REGION" \
  --format='value(peeringNetwork)')"
export PEERING_NAME="demo-aws-peering"

gcloud compute networks peerings create "$PEERING_NAME" \
  --network="$GCP_NETWORK" \
  --peer-network="$PEERING_NETWORK" \
  --stack-type=IPV4_ONLY \
  --import-custom-routes \
  --export-custom-routes

Verify peering is active

gcloud compute networks peerings list --network="$GCP_NETWORK"

You should see STATE: ACTIVE and STATE_DETAILS: Connected.

Note

MTU warning (expected): The create command may warn that your VPC MTU (1460 B) does not match the transport peer MTU (8896 B). This is normal for Partner Cross-Cloud Interconnect Partner Cross-Cloud Interconnect
Partner Cross-Cloud Interconnect — the GCP-side service that accepts the AWS activation key and creates a managed transport for cross-cloud connectivity. . ICMP ping works with the default MTU; large TCP transfers may need MTU tuning in production (GCP docs).

What happens next

After Step 5, GCP GCP
Google Cloud Platform — the cloud provider connected to AWS via Interconnect multicloud in this walkthrough. configuration is complete. The interconnect stays Pending on AWS until backend provisioning finishes — often 5–30 minutes.

Poll in Step 6 (Verify Routing); do not recreate transport or peering while waiting.