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
    • AI Studio
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Cloud Router
    • All guides
    • Getting information about a routing instance
    • Getting a list of operations in a routing instance
    • Create a routing instance
    • Editing routing instance parameters
    • Updating the list of IP prefixes in a routing instance
    • Deleting IP prefixes from a routing instance
    • Adding a private connection to a routing instance
    • Deleting a private connection from a routing instance
    • Deleting a routing instance
    • Cloud Interconnect tutorials
    • All use cases
    • On-prem without redundancy and 1 VPC
    • On-prem without redundancy and multiple VPCs
    • On-prem with redundancy and 1 VPC
    • On-prem with redundancy and multiple VPCs
    • Two separate RIs without on-prem redundancy
    • Even redistribution of on-prem traffic (Active-Active)
    • Prioritizing on-prem traffic based on direction (Active-Standby)
    • On-prem (PRC) connection redundancy via a VPN gateway
    • 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
    • VPC Stithcing. Connectivity for two cloud networks
    • VPC Stitching. Connectivity for two cloud networks and on-prem
  • Access management
  • Release notes
  1. Step-by-step guides
  2. Updating the list of IP prefixes in a routing instance

Updating the list of IP prefixes in a routing instance

Written by
Yandex Cloud
Updated at June 10, 2025

Warning

To request access to this function, contact support.

Note

You need the cloud-router.editor role to run this operation.

CLI
  1. See the description of the CLI command for updating a list of IP prefixes in a routing instance:

    yc cloudrouter routing-instance upsert-prefixes --help
    
  2. Checking the routing instance configuration and the list of IP prefixes:

    yc cloudrouter routing-instance get c3l87**********1dpin
    

    Expected result:

    id: c3l87**********1dpin
    name: ri1
    description: Routing instance 1
    folder_id: b1gqf**********jiz2w
    region_id: ru-central1
    vpc_info:
      - vpc_network_id: c64ck**********jtr7b
        az_infos:
          - manual_info:
              az_id: ru-central1-a
              prefixes:
                - 10.128.0.0/24
    cic_private_connection_info:
      - cic_private_connection_id: cf3td**********nufvr
    status: ACTIVE
    created_at: "2025-03-19T13:35:56Z"
    
  3. Adding prefixes to the list of IP prefixes in the routing instance:

    yc cloudrouter routing-instance upsert-prefixes c3l87**********1dpin \
      --vpc-net id=c64ck**********jtr7b,zone=ru-central1-b,ipv4-prefixes=10.129.0.0/24 \
      --vpc-net id=c64ck**********jtr7b,zone=ru-central1-d,ipv4-prefixes=172.16.1.0/24 \
      --async
    

    Expected result:

     id: al457**********njn6p
     description: routing instance upsert prefixes
     created_at: "2025-03-24T15:24:15.817401507Z"
     created_by: bfbud**********v7dfn
     modified_at: "2025-03-24T15:24:15.817401507Z"
     metadata:
       '@type': type.googleapis.com/yandex.cloud.cloudrouter.v1.UpdateRoutingInstanceMetadata
       routing_instance_id: c3l87**********1dpin
    

    Where:

    • id: ID of the operation performed with a routing instance.
    • description: Description of the operation in progress.
    • created_by: ID of the subject running the operation.
    • async: Running the operation in asynchronous mode. This is the recommended mode for all operations that involve changes to resources.
  4. Check the modified routing instance configuration after the changes:

    yc cloudrouter routing-instance get c3l87**********1dpin
    

    Expected result:

    id: c3l87**********1dpin
    name: ri1
    description: Routing instance 1
    folder_id: b1gqf**********jiz2w
    region_id: ru-central1
    vpc_info:
      - vpc_network_id: c64ck**********jtr7b
        az_infos:
          - manual_info:
              az_id: ru-central1-a
              prefixes:
                - 10.128.0.0/24
          - manual_info:
              az_id: ru-central1-b
              prefixes:
                - 10.129.0.0/24
          - manual_info:
              az_id: ru-central1-d
              prefixes:
                - 172.16.1.0/24
    cic_private_connection_info:
      - cic_private_connection_id: cf3td**********nufvr
    status: ACTIVE
    created_at: "2025-03-19T13:35:56Z"
    

    Where:

    • id: Routing instance ID.
    • name: Routing instance name.
    • description: Routing instance description.
    • folder_id: ID of the cloud folder the routing instance was created in.
    • region_id: Cloud region the routing instance was created in.
    • vpc_info: List of IP prefixes by availability zone. For each zone, prefixes are shown separately.
    • cic_private_connection_info: List of private connections connected to the routing instance.
    • status: Resource state. Target state: ACTIVE. When being updated, it may be in the UPDATING state.
    • created_at: Date and time of resource creation.

Was the article helpful?

Previous
Editing routing instance parameters
Next
Deleting IP prefixes from a routing instance
© 2025 Direct Cursus Technology L.L.C.