GCP Transport (gcloud)

Step 4 — Create the GCP transport

Run from Cloud Shell or a machine with gcloud authenticated to your GCP GCP
Google Cloud Platform — the cloud provider connected to AWS via Interconnect multicloud in this walkthrough. project.

Set environment variables

export GCP_PROJECT="$(terraform output -raw gcp_project_id)"
export GCP_REGION="$(terraform output -raw gcp_region)"
export GCP_NETWORK="$(terraform output -raw gcp_vpc_network_name)"
export TRANSPORT_NAME="$(terraform output -raw gcp_transport_name)"
export ADVERTISED_ROUTES="$(terraform output -raw gcp_advertised_routes_for_transport)"
export ACTIVATION_KEY="paste-activation-key-from-step-3"

gcloud config set project "$GCP_PROJECT"

Create transport

gcloud beta network-connectivity transports create "$TRANSPORT_NAME" \
  --region="$GCP_REGION" \
  --network="$GCP_NETWORK" \
  --advertised-routes="$ADVERTISED_ROUTES" \
  --activation-key="$ACTIVATION_KEY"

Caution

When using --activation-key, bandwidth is embedded in the key — do not pass --bandwidth separately.

Note

The command blocks while the long-running operation completes (Waiting for operation ...). That is normal — do not interrupt unless you intend to cancel the create.

Check status

gcloud beta network-connectivity transports describe "$TRANSPORT_NAME" \
  --region="$GCP_REGION"

Transport states

State	Meaning
CREATING	Long-running create in progress — wait
PENDING_CONFIG	Create finished — proceed to Step 5 immediately
ACTIVE	May appear after AWS interconnect is Available (not required before Step 5)

state: PENDING_CONFIG with a populated peeringNetwork field means Step 4 succeeded. Proceed to VPC Peering.

Full cross-cloud readiness is confirmed when AWS interconnect AWS interconnect
AWS Interconnect – multicloud — a managed private connectivity service that connects Amazon VPCs directly to VPCs on other cloud providers. GA with Google Cloud as of April 2026. is Available and incoming peering routes appear (Step 6).