Networking

Site-to-Site VPN

Connect your infrastructure to the cloud. Site-to-Site VPN connects your on-premises networks to your cloud virtual networks using the industry-standard IPsec and IKE protocols.

OfficeServersFirewallOther data centreServersFirewallIPsec-capableIPsec-capableYour cloud networkGatewaystandby pairServersPermanent IPsec tunnelPermanent IPsec tunnelCloud consoleTunnel statusServers on both sides reach each other across the defined subnets

Keep your business-critical workloads running with a more resilient IT infrastructure

  • Industry-standard Site-to-Site IPsec VPNs

    Connections use Internet Protocol Security (IPsec) and Internet Key Exchange (IKE). IKEv1, IKEv2 and a flexible mode that picks between them automatically are supported; IKEv2 is the default.

  • Highly available and easy to manage

    The IPsec service runs on a cloud gateway that works in active/standby; if the active node fails, the service moves to the standby node. Tunnels are created, updated, switched on or off and deleted in the portal.

  • No extra appliance

    No separate device or virtual machine is installed on the cloud side; the tunnel opens on the gateway you already use. Each office or remote cloud gets its own tunnel on that gateway.

  • Keep your data in Türkiye

    The cloud end of the tunnel and the servers it reaches run in data centres in Türkiye.

Example scenarios

  • A company connecting its head office to the cloud

    The ready parameter list is entered on the office firewall and the tunnel comes up. The head office reaches the cloud servers as if they were on its local network.

  • A team building a lasting link to another cloud

    A second tunnel is defined on the same gateway, each with several local and remote subnets. No separate device is installed on the cloud side.

  • An admin finding out why a tunnel went down

    The tunnel’s state and the IKE error reason show in the portal, so it is clear at once whether the fault is on the office side or the cloud side. When the far end returns, the tunnel comes back up on its own.

Connect your datacentre to the cloud

  • Connect your on-premises networks to the cloud

    Your head office reaches its cloud servers as if they were on the local network, much like setting up and connecting to a remote branch office.

  • Build hybrid connections

    Create a permanent connection between another cloud or datacentre and your cloud networks. Each tunnel carries multiple local and remote subnets.

  • Strong encryption options

    Tunnel traffic is encrypted with AES-128, AES-256 or AES-GCM; key exchange can use SHA-2 digests and Diffie-Hellman groups 14, 15, 16, 19, 20 and 21. Perfect forward secrecy (PFS) is on by default.

  • Key or certificate authentication

    Endpoints authenticate with a pre-shared key or with a certificate validated by a certificate authority. Once saved, a pre-shared key cannot be read back.

  • Parameters most firewalls accept

    You get a ready parameter list for the remote end: IKEv2, DH group 14, SHA2-256, AES-128 or AES-GCM-128, PFS and 60-second dead peer detection. These values match most firewalls as they are.

  • Monitor tunnel status

    Tunnel status and the IKE failure reason are shown in the portal, so you can tell at once whether a problem is on the office side or the cloud side. Dead peer detection notices a lost remote end, and a tunnel in initiator mode re-establishes itself.

Comprehensive security, built in

  • Tunnel mode only

    IPsec runs in tunnel mode only, using ESP (IP protocol 50).

  • Custom encryption profiles

    Instead of the default encryption set, you can choose your own IKE, tunnel and dead peer detection profile.

  • Per-tunnel logging

    Logging can be switched on for each tunnel separately.

Site-to-Site VPN pricing

Pricing is per tunnel. L2 VPN is priced as a separate unit.

Papers, a calculator and a laptop on a desk

Learn more to get started

Technical specifications

Frequently asked questions