Reference

Repository layout

tf-aws-interconnect-demo/
├── versions.tf           # Provider constraints
├── main.tf               # AWS + GCP providers
├── variables.tf          # Input variables
├── outputs.tf            # Values needed for Steps 3–7
├── terraform.tfvars      # Edit before apply
├── aws-interconnect.tf   # Direct Connect Gateway only
├── aws-network.tf        # VPC, VGW, DX association, EC2, SSM endpoints
├── gcp-network.tf        # VPC, subnet, firewall, GCE
├── README.md             # Original walkthrough
├── .gitignore            # Ignores state, local tfvars, demo-gce-key*
└── .terraform.lock.hcl

Step 7 writes demo-gce-key and demo-gce-key.pub locally — both are gitignored and must be removed at teardown.

What is intentionally not in Terraform

Resource	Reason
aws_interconnect_connection	Not yet in hashicorp/aws provider ( issue #47458 ); use console/CLI
google_network_connectivity_transport	Beta API; activation-key flow is console-driven today
VPC peering to transport network	Depends on runtime peeringNetwork from transport describe

External references

AWS Interconnect

• AWS Interconnect – product page
• AWS Interconnect GA blog post (April 14, 2026) — announcement with GCP demo walkthrough
• AWS Interconnect – multicloud regional availability
• AWS Interconnect – multicloud pricing
• AWS Interconnect – multicloud Free Tier announcement
• AWS Interconnect User Guide

GCP Partner Cross-Cloud Interconnect

• GCP Partner Cross-Cloud Interconnect for AWS (overview)
• GCP — VPC peering for AWS-initiated interconnect
• GCP Interconnect pricing

Troubleshooting and community

• AWS re:Post — multicloud interconnect silent failures (SCP / VPC-SC)
• Terraform AWS provider — Interconnect tracking issue #47458

Architecture patterns

• Build resilient multicloud connectivity architectures with AWS Interconnect – multicloud — reference architectures for Transit Gateway and Cloud WAN