Network > VPN Gateway (Site-to-Site VPN) > Overview

This service provides the capability to establish an encrypted network connection between a VPC and a customer's on-premises network.

Concepts

  • Local gateway: A resource allocated to VPN tunnel configuration in NHN Cloud.
  • Remote gateway: A resource allocated to VPN tunnel configuration on the on-premises side.
  • VPN tunnel: An encrypted link that is configured between a remote gateway and a local gateway.

Main Features

  • Enables an encrypted network connection between a VPC and a customer’s on-premises network.
  • The bandwidth (guaranteed on an outbound basis) can be selected among 20M, 50M, 100M, and 1G.
  • The encryption algorithm can be selected among AES192 and AES256.
  • The integrity algorithm can be selected among MD5, SHA1 and SHA256.
  • Network ACLs can be applied.
  • This service is currently available only in the Korea (Pangyo, Pyeongchon, and Gwangju) regions and will be supported by other regions gradually.

Restrictions

Common

  • IPv6 traffic is not supported for VPN connections. Only IPv4 traffic is supported.
  • When connecting your VPC to an on-premises network, you must use address ranges with no overlapping network addresses.
  • You can create one VPN gateway for each VPC.
  • Each VPN gateway can have a maximum of 10 connections.
  • In a VPC connected with VPN, it is not supported to access other networks using peering or access other networks or services through other gateways.
  • By connecting a Transit Hub to a VPC that is already connected via VPN, other projects can also communicate with the on-premises network over VPN.
  • Each VPC has its own VPN Gateway, where the bandwidth can be specified. All VPN connections attached to the same VPN Gateway share the configured bandwidth.
Table of Contents
TOP