Interconnectivity patterns

IBM Cloud Transit Gateway enables you to connect IBM Cloud VPCs and classic infrastructure to transit gateways, allowing you to build global networks of multiple VPCs and classic infrastructure resources across IBM Cloud regions to keep up with your business needs.

IBM Cloud Transit Gateway can connect to classic networks located in any MZR, regardless of the location of the transit gateway or the routing type specified.

Here are some ways that you can implement the IBM Cloud Transit Gateway service.

Use case 1: Interconnect two or more VPCs in the same MZR

Connect two VPCs in the same region with a local transit gateway.

Connect two or more VPCs in the same MZR
Connect two or more VPCs in the same MZR

Use case 2: Interconnect two or more VPCs across multiple MZRs

Connect VPCs in multiple regions by using a global transit gateway.

Connect two or more VPCs across multiple MZRs
Connect two or more VPCs across multiple MZRs

For higher resiliency, you can deploy multiple global transit gateways across regions and group them by using redundancy groups.

Use case 3: Interconnect one or more VPCs in the same MZR and an IBM classic network

Connect VPCs in the same region with IBM Cloud classic through a local transit gateway.

Connect to the IBM classic network and one or more VPCs in the same MZR
Connect to the IBM classic network and one or more VPCs in the same MZR

Use case 4: Interconnect VPCs and an IBM classic network to access all your resources across all MZRs

Connect VPCs from multiple regions with IBM Cloud classic through a global transit gateway.

Connect to the IBM classic network and VPCs to access all your resources across all MZRs
Connect to the IBM classic network and VPCs to access all your resources across all MZRs

Use case 5: Interconnect VPCs across accounts

Connect VPCs in the same region owned by different IBM Cloud accounts through a local transit gateway.

Connect two or more VPCs across accounts
Connect two or more VPCs across accounts

Use case 6: Connect networks (VPC and classic) to multiple local gateways

Keep in mind:

  • Your local traffic is kept on a local transit gateway, which reduces latency.
  • Highly Available (HA) capabilities are provided, as data in VPCs C and D might be replicated in VPCs in E and F.
  • Classic infrastructure transit gateway connections are required to be in the same account as the transit gateway owner.

Connect networks (VPC and classic) to multiple gateways
Connect networks (VPC and classic) to multiple local gateways

Use case 7: Interconnect networks (VPC and classic) across accounts

Connect cross-account IBM Cloud classic accounts to one or more transit gateways. To do so, the IBM Cloud account that owns the transit gateway requests permission from the IBM Cloud classic account to connect it to the transit gateway. The IBM Cloud classic account must approve the request before the connection is made. You can repeat this process for multiple IBM Cloud classic account connections as shown.

Connect both VPC and classic across accounts
Connect both VPC and classic across accounts

Use case 8: Connect networks by using a High Availability GRE tunnel

Connect IBM Cloud classic infrastructure by using a GRE tunnel to a local transit gateway.

This diagram shows a highly available GRE tunnel configuration. When you set up a GRE tunnel configuration, an availability zone must be specified. To make this use case highly available, you must set up two GRE tunnels with the same endpoints, but by using different availability zones.

Connect by using a GRE tunnel
Connect networks using a High Availability GRE tunnel

Transit gateway GRE connections require the gateway owner to specifically configure HA for their needs. A GRE connection is a point-to-point connection, has no built-in redundancy, and is a single point of failure. When you configure a GRE connection on a transit gateway, you must specify the availability zone. For a robust HA solution, configure multiple GRE connections by using different availability zones.

Use case 9: Connect an on-premises network by using Direct Link

Connect IBM Cloud Direct Link to allow on-premises connectivity to IBM Cloud networks through a transit gateway. This connection allows the on-premises network to access all networks that are connected to the transit gateway. In the following example, the Direct Link gateway connects to a global transit gateway, along with 4 VPCs and IBM Cloud Classic Infrastructure. The inverse is also true, in that all other networks that are connected to the transit gateway are now connected to the on-premises network.

Direct Link can be connected to either local or remote transit gateways.

Connect On-Premise Network to Transit Gateway
Connect on-premises network using Direct Link

Use case 10: Using VPN for VPC as a redundant spoke

In this use case, a VPN gateway is configured as a spoke to the transit gateway to provide a redundant network path between the on-premises environment and IBM Cloud. The primary connectivity is established using Direct Link, which offers private, dedicated connectivity with assured bandwidth and low-latency performance. This direct connection terminates in the IBM Cloud Transit VPC, which connects to the transit gateway. From there, traffic is routed to multiple environments including Power Virtual Servers, virtual server instances in spoke VPCs, and classic infrastructure.

To enhance availability without the added cost of a second direct link, a VPN gateway is deployed as a secondary path. This path provides secure connectivity over the internet, using BGP VPN tunnels between the on-prem network and the VPN gateway. Multiple GRE tunnels are established between the VPN gateway appliances and the transit gateway routers, allowing the VPN to act as a spoke within the Transit Gateway topology. While this path doesn't provide the same performance guarantees as Direct Link, it ensures continued connectivity during a primary path failure, making it a cost-effective and resilient solution for hybrid cloud networking.

VPN gateway as a backup connection for Direct Link
VPN gateway as a backup connection for Direct Link

Use case 11: Build a highly available multi-region network

Deploy two global transit gateways in separate regions and group them into a redundancy group to create a resilient network architecture. In this example, Global Transit GW A is deployed in eu-es and Global Transit GW B is deployed in br-sao. Both gateways are members of the same redundancy group.

Two VPCs under Account A are connected to both transit gateways:

  • VPC A (us-south, 10.4.0.0/16) — connects locally to Transit GW A or B, and reaches VPC B (10.5.0.0/16) via Transit GW A or B
  • VPC B (us-east, 10.5.0.0/16) — connects locally to Transit GW A or B, and reaches VPC A (10.4.0.0/16) via Transit GW A or B

Because each VPC is connected to both transit gateways, traffic can be routed through either gateway. If one region becomes unavailable, the other gateway continues to forward traffic between the VPCs without interruption.

Build a highly available multi-region network
Build a highly available multi-region network

Use case 12: Zone-resilient VPN connectivity using a regional VPN gateway

In this use case, a regional VPN gateway provides resilient connectivity between an on-premises network and IBM Cloud through Transit Gateway. The gateway deploys two VPN appliances across separate availability zones within a VPC, eliminating a single point of failure.

The on-premises environment establishes a BGP VPN connection to the VPN gateway. Each VPN appliance establishes GRE tunnels to both Transit Gateway routers, creating multiple redundant paths between the VPN gateway and Transit Gateway. eBGP exchanges routes over these tunnels, enabling dynamic routing between the on-premises environment and IBM Cloud.

Transit Gateway extends connectivity to attached resources, including VPCs, Classic Infrastructure, PowerVS workspaces, and Direct Link connections. If a VPN appliance or availability zone becomes unavailable, traffic automatically uses alternate paths through the remaining appliance and GRE tunnels, maintaining connectivity without requiring manual failover.

This architecture is well suited for hybrid cloud environments that require highly available, zone-resilient connectivity to IBM Cloud resources while simplifying failover management and reducing operational complexity.

Zone-resilient VPN connectivity using a regional VPN gateway
Zone-resilient VPN connectivity using a regional VPN gateway

Beta

Use case 13: Single-zone dynamic route server with Transit Gateway

In this use case, a VPC dynamic route server is connected to a transit gateway to enable automatic, BGP-based route distribution across connected networks. An Edge VPC acts as the network entry point, hosting a firewall and a dynamic route server appliance. The enterprise network connects to IBM Cloud over Direct Link, while a public address range provides internet-facing connectivity.

Within the Edge VPC, the firewall establishes an eBGP session with the dynamic route server. The dynamic route server connects to the transit gateway, which establishes GRE tunnels to the dynamic route server appliances and runs eBGP sessions over those tunnels. In this single-zone deployment, three dynamic route server appliances connect to two transit gateway devices, creating six GRE tunnels in a full mesh for redundancy.

The dynamic route server acts as a read-only spoke: it learns routes advertised by the transit gateway across its connections and distributes those routes to BGP peers within the VPC, including the firewall. This eliminates the need to manually maintain static routes as the network grows or changes. From the transit gateway, traffic is routed to connected environments, including classic infrastructure, Power Virtual Server workspaces, and spoke VPCs.

This use case is well suited for hybrid cloud environments that require dynamic, scalable route propagation across multiple networks without the overhead of managing static routes or separate VPN tunnels for each destination.

Single-zone dynamic route server with Transit Gateway{: caption="[Single-zone dynamic rou te server with Transit Gateway" caption-side="bottom"}

Beta

Use case 14: Multi-zone dynamic route server with Transit Gateway

In this use case, dynamic route server appliances are deployed across multiple VPC zones and connected to a transit gateway to provide highly available, BGP-based route distribution between IBM Cloud and enterprise networks. An Edge VPC serves as the network entry point, hosting firewall and dynamic route server appliances that connect on premises networks, internet traffic, and cloud workloads through a centralized routing architecture.

The firewall establishes eBGP sessions with the dynamic route server appliances, while the transit gateway creates GRE tunnels and eBGP sessions with dynamic route server appliances in each zone. By distributing appliances across three zones and maintaining redundant connections to transit gateway devices, the design continues to exchange routing information even if a device, tunnel, or entire zone becomes unavailable.

The dynamic route server appliances learn routes from the transit gateway and advertise them to BGP peers within the VPC, including the firewall. This enables automatic route propagation between the enterprise network and IBM Cloud resources, including classic infrastructure, Power Virtual Server workspaces, and spoke VPCs, without requiring manual route updates as the environment evolves.

This use case is well suited for business-critical hybrid cloud deployments that require resilient, multi-zone connectivity and automated route distribution across a large and growing network footprint.

Multi-zone dynamic route server with Transit Gateway
Multi-zone dynamic route server with Transit Gateway

Power Virtual Server use cases using Transit Gateway

For use cases involving Power Virtual Server workspaces, see Power Edge Router use cases.