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.
Terraform in Yandex Cloud
  • Getting started
  • Solution library
    • Overview
    • Release notes
          • vpc_address
          • vpc_gateway
          • vpc_network
          • vpc_private_endpoint
          • vpc_route_table
          • vpc_security_group
          • vpc_security_group_rule
          • vpc_subnet

In this article:

  • Example usage
  • Schema
  • Optional
  • Read-Only
  • Nested Schema for static_route
  1. Terraform reference
  2. Resources
  3. Virtual Private Cloud (VPC)
  4. Data Sources
  5. vpc_route_table

yandex_vpc_route_table (Data Source)

Written by
Yandex Cloud
Updated at September 11, 2025
  • Example usage
  • Schema
    • Optional
    • Read-Only
    • Nested Schema for static_route

Get information about a Yandex VPC route table. For more information, see Yandex Cloud VPC.

This data source is used to define VPC Route Table that can be used by other resources.

Warning

One of route_table_id or name should be specified.

Example usageExample usage

//
// Get information about existing VPC Route Table.
//
data "yandex_vpc_route_table" "my_rt" {
  route_table_id = "my-rt-id"
}

SchemaSchema

OptionalOptional

  • folder_id (String) The folder identifier that resource belongs to. If it is not provided, the default provider folder-id is used.
  • name (String) The resource name.
  • route_table_id (String) Route table ID.

Read-OnlyRead-Only

  • created_at (String) The creation timestamp of the resource.
  • description (String) The resource description.
  • id (String) The ID of this resource.
  • labels (Map of String) A set of key/value label pairs which assigned to resource.
  • network_id (String) ID of the network this route table belongs to.
  • static_route (Set of Object) (see below for nested schema)

Nested Schema for Nested Schema for static_route

Read-Only:

  • destination_prefix (String) Route prefix in CIDR notation.

  • gateway_id (String) ID of the gateway used ad next hop.

  • next_hop_address (String) Address of the next hop.

Was the article helpful?

Previous
vpc_private_endpoint
Next
vpc_security_group
© 2025 Direct Cursus Technology L.L.C.