VPN & Hybrid Connectivity
Connect offices, data centers, and remote staff privately to your VPC.
View Service DetailsMost enterprise workloads need private connectivity between the cloud and existing sites. The platform offers three options that can be combined.
Connectivity Options
| Option | What it connects | Notes |
|---|---|---|
| Site-to-site IPSec VPN | Your office/DC firewall ↔ your VPC | Standard IKEv2; works with common firewall vendors |
| Client SSL VPN | Individual laptops ↔ your VPC | Per-user credentials + MFA; ideal for admins and remote staff |
| Dedicated connection | Your premises ↔ platform edge | Private circuit for steady high-volume or latency-sensitive traffic |
Setting Up Site-to-Site IPSec
Create the VPN gateway
Networking → VPN → Create Gateway inside the target VPC. Note its public address.
Define the connection
Enter the peer (your firewall’s public IP), a strong pre-shared key, and the IKE/ESP parameters. Sensible defaults (IKEv2, AES-256, SHA-256, DH group 14) are pre-selected.
Declare both networks
Local: your VPC subnets. Remote: your on-premises CIDRs. These become the encryption domain and routes on the virtual router.
Mirror on your firewall and verify
Configure the matching tunnel on your on-premises device. The console shows tunnel state, and a built-in ping test validates end-to-end reachability.
Routing and Failover
Connections support dead-peer detection and automatic re-establishment. For critical sites, create two tunnels from redundant firewalls; the router prefers the healthy path automatically.
Remember: VPN routing requires non-overlapping address space. If your office also uses 10.0.0.0/16, re-plan one side before connecting.