12 min read

Learning Objectives

By the end of this module, you will be able to:

  • Choose between VPN Gateway, Cross Connect and Cloud Connect for a given pair of networks, region and bandwidth requirement
  • Design a VPN Gateway with the right protocol, tier and high-availability option, and plan the static routes it requires
  • Design private-tier egress with the Managed NAT Gateway, including its SNAT rules and guest routing
  • Plan the role of each link during a migration cutover
  • Provision an IPSec tunnel on a VPN Gateway and a NAT Gateway for private egress in the Data Center Designer (DCD)

Unit 3.6: Hybrid Connectivity: VPN, NAT, and Cross-Connect

Introduction

FinCorp's production VDC does not stand alone. It must reach the company's own data centers during the VMware migration, a recovery VDC in Berlin, a second Frankfurt VDC for AI workloads, and the internet for patches and external APIs, all without giving any private tier a public interface. Four platform components answer these needs, and each has a hard scope.

This unit maps each link to the component whose scope fits it, then builds the two that every FinCorp environment needs: a VPN tunnel and a NAT Gateway for private egress.

1. The Four Connectivity Components

Link Component Scope that decides
VDC to on-premises, over the internet VPN Gateway (IPSec or WireGuard) Any reachable public endpoint; encrypted; static routing
VDC to VDC in another region VPN Gateway No region constraints between VDCs
VDC to VDC, same region and contract Cross Connect Same region, same contract, private LANs, one IP range
Company network to VDC over a dedicated line Cloud Connect VDC in Frankfurt (DE/FRA), Berlin (DE/TXL) or Las Vegas (US/LAS), and a dedicated line to that data center
Private VMs to the internet, outbound only Managed NAT Gateway Private LANs only; SNAT

As shown above, region and contract boundaries decide most choices before bandwidth does. FinCorp's Frankfurt core and Berlin recovery VDC are in different regions, so their link is a VPN Gateway, not a Cross Connect.

1.2 VPN Gateway

The VPN Gateway is a managed service for encrypted connectivity between VDC resources and remote networks. It supports IPSec and WireGuard; using both at once requires a separate gateway per protocol. IPSec uses IKEv2 only, with pre-shared key (PSK) authentication; a strong 32-character PSK is recommended. WireGuard uses public and private key pairs with ChaCha20 and Poly1305. The product does not auto-create PSKs or key pairs: the DCD tunnel form generates a PSK only when you ask it to, and WireGuard keys come from your own tools. Key storage and rotation are part of your runbook.

The routing model is the main design constraint. Only static routing is supported; dynamic routing and BGP are not available. You define the cloud and peer network CIDRs per IPSec tunnel (up to 20 on each side) or the allowed IPs per WireGuard peer (up to 20). Then every host on the connected LANs needs a route to the peer subnets via the gateway's LAN address, because adding those routes to LAN hosts cannot be automated by the service. Make the routes persistent in the guest image or your configuration management.

Further limits shape placement. All LANs connected to a gateway must belong to the same VDC. The tunnel endpoint and gateway IP addresses are IPv4 only, while the traffic inside the tunnel can be IPv4 and IPv6. The interface IP is not DHCP aware, so it belongs in the reserved range of the LAN (Unit 3.1). Each tunnel supports up to 1 Gbps. A region holds up to eight VPN gateways per contract by default. A gateway cannot connect directly to LANs managed by Managed Kubernetes; attach an additional LAN to the node pool and connect that LAN instead. And the gateway must be deleted before its VDC.

Tiers set capacity, and High Availability adds an active-passive pair:

Tier Resources Description
Standard VPN <br> Standard VPN + High Availability A maximum of five LANs and 10 IPSec Tunnels or WireGuard Peers. You can upgrade the tier to Enhanced VPN or Premium VPN with or without high availability.
Enhanced VPN <br> Enhanced VPN + High Availability A maximum of 10 LANs and 20 IPSec Tunnels or WireGuard Peers. You can upgrade the tier to Premium VPN with or without high availability.
Premium VPN <br> Premium VPN + High Availability A maximum of 15 LANs and 30 IPSec Tunnels or WireGuard Peers. It is highly recommended for mission-critical or production workloads.

As shown above, tiers can be upgraded but not downgraded, so start at the smallest tier that fits the planned tunnel count and upgrade when waves add sites. The price is per provisioned gateway, and data transmission is charged as regular traffic:

VPN Gateway type Price per hour Price group
Standard 0,032 € PG D
Standard (High Availability) 0,064 € PG D
Enhanced 0,076 € PG D
Enhanced (High Availability) 0,15 € PG D
Premium 0,20 € PG D
Premium (High Availability) 0,40 € PG D

You choose the gateway's maintenance start (day and UTC time); maintenance then runs in a 4-hour window, during which only the name and description can be updated.

1.3 Managed NAT Gateway

The NAT Gateway gives private VMs outbound internet access without a public interface. It performs Source NAT (SNAT): VMs initiate connections and receive responses, and the gateway does not accept connections initiated from the internet. There is no Destination NAT (DNAT), so it is never an inbound path; inbound traffic goes through the ALB or NLB.

Its scope is private. Only private LANs can be connected, up to six per gateway, and a LAN connected to a NAT Gateway cannot be changed from private to public. It supports TCP, UDP and ICMP, requires reserved public IP addresses (several per gateway are possible), and records flow logs. A contract holds five NAT Gateways by default, adjustable through support. The basic fee is 0,04 € per hour, with no processing fee for data.

Two configuration facts cause most failures. First, SNAT rules can be configured only after the gateway has been provisioned. Each rule names the protocol, the public IP used to mask the source, the source subnet, and optionally a target subnet and port range, which lets you restrict egress to trusted destinations. Second, the gateway's route is not injected into the VMs. You must point the default route of each private VM at the gateway's private IP, or create a dedicated route per external target. If a VM with its default route on the gateway needs DNS, a UDP SNAT rule for DNS must exist, or name resolution fails.

1.4 Cross Connect

Cross Connect joins VDCs in the same region and the same contract through a private LAN. It is free to use, and its bandwidth is comparable to normal private NICs. It is generally available in Berlin (de/txl), Frankfurt (de/fra/1 and de/fra/2) and London (gb/lhr), and can connect all of your VDCs in those regions; elsewhere it is in Early Access, which is not for production.

The connected LANs behave as one network. The NICs of all VDCs on a Cross Connect must be in the same IP range, each IP address may be used by only one instance, and a LAN can be associated with a single Cross Connect. In practice that means a shared address plan across VDCs, with non-overlapping static or DHCP ranges, or your own DHCP server. Contract owners and administrators can create Cross Connects; other users need the Create Cross Connects privilege. A Cross Connect can be deleted only after every LAN and VDC is disconnected.

1.5 Cloud Connect

Cloud Connect creates a direct, dedicated Layer-3 connection between a company network and a VDC. It requires a VDC at Frankfurt, Berlin or Las Vegas and a dedicated line to that data center, for example dark fibre or MPLS contracted from a telecommunications company. The 24/7 Enterprise Level Support assists with the connection. It is a procurement project rather than a console build, so plan its lead time before the migration waves that need it.

FinCorp's plan uses each link for what its scope allows:

Phase Link Why
First waves and testing IPSec VPN Gateway, Premium with High Availability, from the on-premises VMware site to fc-app Available immediately; 1 Gbps per tunnel; several tunnels for parallel waves
Bulk waves Cloud Connect from the Frankfurt site to fc-prod-fra-core Dedicated line for sustained data transfer; ordered months ahead
Recovery site VPN Gateway between fc-prod-fra-core and fc-prod-txl-dr Different regions rule out Cross Connect
AI VDC in Frankfurt Cross Connect between fc-prod-fra-core and fc-prod-fra-ai Same contract and region; free; shared IP range planned up front
Private egress NAT Gateway fc-nat-app on fc-app Patches, external APIs and AI inference calls without public interfaces

Two cutover rules follow from the routing model. Because routes are static and set on hosts, every wave's route changes are scripted and reversed in the rollback plan. And because the on-premises and cloud subnets must not overlap for routing to work, the address plan from Unit 3.1 is checked against the on-premises ranges before the first tunnel. Unit 7.4 builds the wave plan on these links.

DCD Implementation Walkthrough

You will provision an IPSec tunnel from fc-prod-fra-core to the on-premises site, and a NAT Gateway that gives fc-app outbound access. Both use the reserved addresses from Unit 3.1.

Prerequisites: two free addresses in the fc-prod-fra-edge block in Frankfurt; free LAN addresses between .2 and .9 on fc-app; the Access and manage VPN Gateway privilege and the Create Internet Access permission, or the Administrator role; the on-premises gateway's public address and subnets.

Build goal: Provision a VPN Gateway tunnel; provision a NAT Gateway for private egress.

Steps, part A: VPN Gateway (in the Data Center Designer):

  1. Go to Menu > Network Services > VPN Gateway and select Create VPN Gateway.
  2. In Properties, enter Name fc-vpn-onprem, choose the Frankfurt Location, and select a reserved IP Address from the same location.
  3. In Tier, choose Premium VPN and select High Availability. In Protocol, choose IPSec; the Version is IKEv2.
  4. In LAN Connections, select fc-prod-fra-core as Datacenter, select Add LAN Connection, choose fc-app and enter the gateway's IPv4 CIDR with an address from .2 to .9 that is not in use.
  5. Set the maintenance DAY and TIME (UTC) outside the migration windows, and select Save. The state is PROVISIONING, then AVAILABLE.
  6. Select Create Tunnels. Enter the Tunnel name, the Remote host (public IPv4 or FQDN) and a Pre-shared key (PSK) of 32 characters. Choose matching Diffie-Hellman Group, Encryption Algorithm, Integrity Algorithm and Lifetime for the IKE and ESP phases, for example AES256-GCM-16 with SHA256. Enter the Cloud Network CIDRs and Peer Network CIDRs, and select Save.
  7. Configure the on-premises device with the same parameters, then add a persistent route on each fc-app host to the on-premises subnets via the gateway's LAN address, and the reverse routes on premises.

Steps, part B: NAT Gateway (in the Data Center Designer):

  1. Open fc-prod-fra-core, add a NAT Gateway element and connect its interface to the private LAN fc-app.
  2. In the Settings tab, enter the name fc-nat-app and add a public IP from the reserved addresses.
  3. Provision the changes. The NAT rules can be configured only after this first provisioning.
  4. Open the Gateway IPs tab. To move the gateway's private address into the planned .2 to .9 slot, select Remove IP for the current address, then Add IP with the new one.
  5. In NAT Rules, select Create SNAT Rule: enter a name, choose TCP, select the gateway's Public IP, enter the fc-app subnet as Source Subnet, and restrict Target Subnet and Port range where only known services are allowed. Select Create.
  6. Create a second rule for UDP to the DNS resolvers on port 53, so that name resolution works through the gateway.
  7. Provision the changes, then set the default route of each fc-app VM to the gateway's private IP in the guest operating system.

Common mistakes:

  • Planning a Cross Connect between Frankfurt and Berlin. It requires the same region and contract; use the VPN Gateway.
  • Expecting BGP to learn routes. Only static routing exists; host routes are your configuration.
  • Placing the VPN interface or NAT private address in the DHCP range. Both belong in .2 to .9.
  • Trying to create SNAT rules before the NAT Gateway is provisioned.
  • Forgetting the guest default route, or the UDP rule for DNS. The gateway does not inject routes.
  • Using the NAT Gateway for inbound access. It is SNAT only.
  • Deleting the VDC before the VPN Gateway attached to it.

Summary

Hybrid connectivity on IONOS CLOUD is a choice among four scoped components. The VPN Gateway links any two sites with encrypted, statically routed tunnels, across regions if needed, and offers active-passive HA per tier. Cross Connect joins VDCs privately and free of charge, but only within one region and contract and one IP range. Cloud Connect brings a dedicated line into Frankfurt, Berlin or Las Vegas. The NAT Gateway gives private tiers outbound access, with routes and SNAT rules that you configure explicitly.

Key Points:

  • VPN Gateway: IPSec with IKEv2 and PSK, or WireGuard; static routing only; up to 1 Gbps per tunnel; tiers upgrade but never downgrade.
  • Hosts need routes to the peer subnets via the gateway's LAN address; the service does not add them.
  • NAT Gateway: SNAT only, private LANs only, rules after provisioning, guest default route set by you.
  • Cross Connect: same region, same contract, private LANs, one IP range, one Cross Connect per LAN.
  • Cloud Connect: a dedicated line into a VDC at Frankfurt, Berlin or Las Vegas.