Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Yandex Virtual Private Cloud
  • Getting started
    • All tutorials
    • Architecture and protection of a basic internet service
    • DHCP settings for working with a corporate DNS server
      • Solution architecture
      • Unaided implementation with Yandex Cloud
      • SGW solution by the Yandex Cloud architect team
    • Installing the Cisco CSR 1000v virtual router
    • Installing the Mikrotik CHR virtual router
    • Connecting to a cloud network using OpenVPN
    • Configuring Cloud DNS to access a Managed Service for ClickHouse® cluster from other cloud networks
    • Secure user access to cloud resources based on WireGuard VPN
    • Creating and configuring a UserGate gateway in proxy server mode
    • Creating and configuring a UserGate gateway in firewall mode
    • Implementing fault-tolerant use cases for network VMs
    • Creating a tunnel between two subnets using OpenVPN Access Server
    • Creating a bastion host
    • Migrating an HDFS Yandex Data Processing cluster to a different availability zone
    • Configuring a network for Yandex Data Processing
    • Network between folders
    • Implementing a secure high-availability network infrastructure with a dedicated DMZ based on the Check Point NGFW
    • Cloud infrastructure segmentation with the Check Point next-generation firewall
    • Connecting to Object Storage from Virtual Private Cloud
    • Connecting to Container Registry from Virtual Private Cloud
    • Using Yandex Cloud modules in Terraform
    • Deploying an Always On availability group with an internal network load balancer
    • Configuring Cloud Interconnect access to cloud networks behind NGFWs
    • Automating tasks using Managed Service for Apache Airflow™
    • Setting up network connectivity between BareMetal and Virtual Private Cloud subnets
  • DDoS Protection
  • Access management
  • Terraform reference
  • Audit Trails events
  • Release notes
  • FAQ
  1. Tutorials
  2. Setting up network connectivity with IPsec gateways
  3. Solution architecture

Setting up network connectivity between cloud and remote resources with IPsec gateways

Written by
Yandex Cloud
Updated at March 14, 2025

Network connectivity between your corporate data center and cloud resources must be properly protected. For this purpose, you can use secure connections.

One of the technologies used for that is an internet connection through IPsec gateways over the IPsec protocol. IPsec is widely used on a variety of network devices, both physical and virtual.

Cloud site:

  • Network named cloud-net with the following subnets: subnet-a (172.16.1.0/24), subnet-b (172.16.2.0/24), and ipsec-subnet (172.16.0.0/24).
  • Main IPsec gateway named cloud-gw as a VM based on the open-source strongSwan solution. Connect this IPsec gateway to ipsec-subnet. The main goal of the gateway is to set up an IPsec connection to a remote gateway and provide network connectivity between test VMs.
  • cloud-net-sg security group is used for the VM network interface of the main gateway and allows IPsec traffic between the gateways.
  • cloud-net-rt route table with static routes ensures traffic towards subnet-1 of the remote site through the main IPsec gateway.
  • Ubuntu Linux-based test VMs, vm-a and vm-b, get connected to subnet-a and subnet-b, respectively. These VMs are used to check IP connectivity via an IPsec connection.

Remote site:

  • remote-net network with subnet-1 (10.10.0.0/16).
  • Remote IPsec gateway named remote-gw as a VM based on the open-source strongSwan solution. Connect this IPsec gateway to subnet-1. The main goal of the gateway is to set up an IPsec connection to the main gateway and provide network connectivity between test VMs.
  • remote-net-sg security group is used for the VM network interface of the remote gateway and allows IPsec traffic between the gateways.
  • remote-net-rt route table with static routes ensures traffic towards subnet-a and subnet-b of the cloud site through the remote IPsec gateway.
  • Ubuntu Linux-based test VM, vm-1, gets connected to subnet-1. This VM is used to check IP connectivity via an IPsec connection.

The IPsec connection is established between the public IP addresses of the main gateway (x1.x1.x1.x1) and those of the remote one (x2.x2.x2.x2).

To set up network connectivity with IPsec gateways, use one of the following methods:

  • Security GateWay solution by the Yandex Cloud architect team
  • Setting up network connectivity with IPsec gateways on your own using Yandex Cloud

Was the article helpful?

Previous
Terraform
Next
Unaided implementation with Yandex Cloud
Yandex project
© 2025 Yandex.Cloud LLC