EMEALAB IXMC Testbed

AWS ↔ GCP hub · live operations view

Waiting for data

Topology

Healthy Provisioning Unhealthy Unknown Quarantined attachment

Loading topology…

Interconnect

—

Direct Connect Gateway

—

Cloud WAN

—

Attachments

0

Every Cloud WAN attachment, across all owning accounts.

CloudWAN Routes

The route tables for every segment and Core Network Edge. Loaded on demand, straight from the live core network.

GCP Partner Interconnect Multicloud

Static

Peer

From the GCP Terraform module — the collector observes the AWS side only.

Compute instance

Diagnostic VM reachable over the VPC and, via the interconnect, from AWS (RFC1918 only). SSH is IAP-only.

Live telemetry

Live RTT, packet loss and health from the CloudWatch Network (Synthetic) Monitors — ICMP to the VM and TCP per listener.

Test command Service Protocol Port Endpoint RTT Packet loss NHI

Accounts

0

Owners of attachments and RAM principals.

RAM sharing

Resource Access Manager share of the core network.

Architecture

How it's provisioned — GitLab control plane, the AWS account and GCP project, and the cross-cloud interconnect that joins them.
Architecture diagram: a GitLab CI/CD control plane provisions an AWS account and a GCP project, keyless into both clouds, joined by a Partner Cross-Cloud Interconnect between AWS Cloud WAN (with a Direct Connect Gateway) and the GCP VPC.