Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Cloud Router
    • All use cases
    • On-premises without redundancy and one cloud network
    • On-premises without redundancy and multiple cloud networks
    • On-premises with redundancy and one cloud network
    • On-premises with redundancy and multiple cloud networks
    • Two separate route instances without on-premises redundancy
    • Even redistribution of on-premise traffic (Active-Active)
    • Prioritizing on-premise traffic based on direction (Active-Standby)
    • Reserving an on-premise connection via a VPN gateway (PRC)
    • Prioritizing a static VPC route over routes from PRC
    • Even traffic distribution for route 0.0.0.0/0
    • Prioritizing traffic by direction for route 0.0.0.0/0
    • Connectivity for two cloud networks
    • Connectivity for two cloud networks and on-premises
  • Access management
  • Release notes
  1. Use cases
  2. On-premises without redundancy and one cloud network

On-prem without redundancy and 1 VPC

Written by
Yandex Cloud
Updated at November 10, 2025

Non-reserved on-prem connection via a single Cloud Interconnect private connection to a single RI with a single VPC cloud network.

The network topology is presented on the diagram in the following configuration:

  • On-Prem client with two local subnets: subnet-c1 and subnet-c2.
  • On-prem network hardware connects to the Yandex Cloud network hardware via Cloud Interconnect.
  • prc-m9 private connection established via the M9 point of presence connects to RI in Yandex Cloud.
  • On the Yandex Cloud side, the Net-1 virtual network comprised of three subnets, subnet-a1, subnet-b1, and subnet-d1, connects to RI.

This topology enables network connectivity between On-Prem subnets and Net-1 VPC subnets.

Was the article helpful?

Previous
All use cases
Next
On-premises without redundancy and multiple cloud networks
© 2025 Direct Cursus Technology L.L.C.