Options for connecting to remote infrastructure
VK Cloud allows you to configure different options for connecting to remote infrastructure using a VPN tunnel. The choice of connection option depends on the following factors:
- the project's SDN type;
- the availability of internet access from the remote infrastructure;
- the fault tolerance requirements for the connection.
Connection | Description | Limitations |
|---|---|---|
The remote infrastructure connects to VK Cloud via a VPN tunnel based on a standard router. This option is suitable for simple scenarios: connectivity between the cloud and a small remote network |
| |
The remote infrastructure connects to VK Cloud through the Cloud Direct Connect network using the BGP protocol. The VPN tunnel is created based on an advanced router to which the network with the project's cloud infrastructure is connected. The remote infrastructure may not have internet access. This option is used for hosting in the cloud an application that does not require fault-tolerant network connectivity, as well as for internet access from an On-premises closed infrastructure |
| |
The remote infrastructure connects to VK Cloud through the Cloud Direct Connect network using the BGP protocol. The VPN tunnel is created based on an advanced router. The project's cloud infrastructure is located in a network connected to a standard router, which is linked to the advanced router via static routes. The remote infrastructure may not have internet access. This option allows you to connect On-premises infrastructure to an existing VK Cloud project, as well as to projects with Floating IP addresses and PaaS services | Only in SDN Sprut | |
The remote infrastructure connects to VK Cloud using the BGP protocol via two independent Cloud Direct Connect communication channels laid to two different availability zones. The advanced router is connected to both channels and to the standard router, which routes traffic to objects inside the project in VK Cloud. The remote infrastructure may not have internet access. This option provides fault-tolerant network connectivity between the remote infrastructure and the project in VK Cloud with minimal downtime when switching between communication channels | Only in SDN Sprut | |
Fault-tolerant connection via two Direct Connect channels and VRRP | The remote infrastructure connects to VK Cloud using the BGP protocol via two independent Cloud Direct Connect communication channels laid to two different availability zones. Separate advanced routers are connected to each of the communication channels, linked to the project's standard router via VRRP (a virtual IP address). The remote infrastructure may not have internet access. This option provides seamless fault-tolerant network connectivity between the remote infrastructure and the project in VK Cloud | Only in SDN Sprut |
The remote infrastructure connects to VK Cloud via VPN using the IPsec protocol. The VPN tunnel is created based on an advanced router to which the network with the project's cloud infrastructure is connected. The remote infrastructure must have internet access. This option provides secure access from On-premises infrastructure to VK Cloud without the Cloud Direct Connect technology. |
| |
Via IPsec, an advanced router and a standard router | The remote infrastructure connects to VK Cloud via VPN using the IPsec protocol. The VPN tunnel is created based on an advanced router. The project's cloud infrastructure is located in a network connected to a standard router, which is linked to the advanced router via static routes. The remote infrastructure must have internet access. This option allows you to connect On-premises infrastructure to an existing VK Cloud project, as well as to projects with Floating IP addresses and PaaS services, without the Cloud Direct Connect technology |
|