Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • 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
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Virtual Private Cloud
  • Getting started
    • All guides
      • Creating a static route
      • Creating and setting up a NAT gateway
      • Getting NAT gateway info
      • Moving a route table between folders
      • Getting route table info
      • Moving a NAT gateway between folders
      • Deleting a route table
      • Deleting a NAT gateway
    • Enabling a software-accelerated network
    • Chart of network connections
    • Viewing operations with resources
  • DDoS Protection
  • Access management
  • Pricing policy
  • Terraform reference
  • Metrics Monitoring
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

  • Examples
  • Route table in the current folder
  1. Step-by-step guides
  2. Static routing
  3. Moving a route table between folders

Moving a route table to a different folder

Written by
Yandex Cloud
Updated at July 13, 2026
View in Markdown
  • Examples
    • Route table in the current folder

You can move cloud resources between folders within a single cloud.

Management console
CLI
API

To move a route table to another folder:

  1. In the management console, select the folder containing your routing table.
  2. Navigate to Virtual Private Cloud.
  3. In the left-hand panel, select Routing tables.
  4. Click in the row of the table to move and select Move.
  5. Select the destination folder from the drop-down list.
  6. Click Move.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

To move a route table to another folder:

  1. View the description of the CLI command for moving route tables:

    yc vpc route-table move --help
    
  2. Get the name or ID of the route table to move:

    yc vpc route-table list
    

    Result:

    +----------------------+---------+-------------+----------------------+
    |          ID          |  NAME   | DESCRIPTION |      NETWORK-ID      |
    +----------------------+---------+-------------+----------------------+
    | enp8c7ia88i8******** | table-1 |             | encb4ubvmief******** |
    +----------------------+---------+-------------+----------------------+
    
  3. Get a list of available folders:

    yc resource-manager folder list
    

    Result:

    +----------------------+------------------------+--------+--------+
    |          ID          |          NAME          | LABELS | STATUS |
    +----------------------+------------------------+--------+--------+
    | b1cs8ie21pk1******** | default                |        | ACTIVE |
    | b1chgf288nvg******** | my-folder-1            |        | ACTIVE |
    | b1cu6g9ielh6******** | my-folder-2            |        | ACTIVE |
    +----------------------+------------------------+--------+--------+
    
  4. Move the route table by specifying the name or ID of the table and destination folder:

    yc vpc route-table move <route_table_name_or_ID> \
      --destination-folder-name <destination_folder_name> \
      --destination-folder-id <destination_folder_ID>
    

    Use either --destination-folder-name or --destination-folder-id.

    If the route table is not in the current folder (default folder), specify the source folder using --folder-name or --folder-id.

    Result:

    id: enp8c7ia88i8********
    folder_id: b1chgf288nvg********
    created_at: "2022-10-10T05:55:39Z"
    name: table-1
    network_id: encb4ubvmief********
    

    For more information about the yc vpc route-table move command, see the CLI reference.

To move a route table to a different folder, use the move REST API method for the RouteTable resource or the RouteTableService/Move gRPC API call, and provide the following in the request:

  • ID of the route table you need to move in the routeTableId parameter.

    To get the route table ID, use the list REST API method for the RouteTable resource or the RouteTableService/List gRPC API call and provide the current folder ID in the folderId request parameter.

  • ID of the folder the route table will be moved to in the destinationFolderId parameter.

    To learn how to find out the folder ID, see Getting the folder ID.

ExamplesExamples

Route table in the current folderRoute table in the current folder

Move a route table from the current folder by specifying the table name and destination folder name:

CLI
yc vpc route-table move table-1 \
  --destination-folder-name my-folder-1

Useful linksUseful links

  • Moving a cloud network to a different folder
  • Moving a subnet to a different folder

Was the article helpful?

Previous
Getting NAT gateway info
Next
Getting route table info
© 2026 Direct Cursus Technology L.L.C.