Skip to content
AWS-GCP Interconnect

Troubleshooting

Quick reference

Section titled “Quick reference”
SymptomLikely causeFix
Interconnect stuck PendingGCP transport or peering not created; AWS provisioningComplete Steps 4–5; check AWS console; wait 15–30 min

aws interconnect invalid choice

AWS CLI too old (< 2.34.43)Use console for status, or upgrade CLI
GCP list-routes shows 0 incomingAWS interconnect not Available yetWait for AWS Available; then re-check
Transport PENDING_CONFIG after peeringNormal until AWS backend completesCheck AWS status; peering ACTIVE is GCP-side success

aws_dx_gateway_association pending

Interconnect not active yetWait for Available; check activation key
EC2 SSM session failsVPC endpoints not ready or IAMWait 2–3 min after apply; confirm SSM agent
GCE SSH via IAP failsMissing IAP firewall rule

Rule demo-allow-iap-ssh allows 35.235.240.0/20

Ping fails both waysRoute or peering issue

Re-check —import-custom-routes / —export-custom-routes

Wrong region pairUnsupported Interconnect path

Run remote-profiles list; align regions

Free Tier billing errorQuota used or eligibility failedUse paid multicloud — see Billing Verification
MTU warning at peering createDefault GCP VPC MTU vs transport jumbo MTUExpected — safe for ICMP; tune for large TCP

Interconnect failed (no error)

Org SCP blocking interconnect:* or VPC-SC

See Checking for Errors

Subsections

Section titled “Subsections”