yandex_vpc_subnet (DataSource)
Статья создана
Обновлена 23 сентября 2026 г.
Get information about a Yandex VPC subnet. For more information, see Yandex Cloud VPC.
This data source is used to define VPC Subnets that can be used by other resources.
Важно
One of subnet_id or name should be specified.
Example usage
//
// Get information about existing VPC Subnet.
//
data "yandex_vpc_subnet" "admin" {
subnet_id = "my-subnet-id"
}
Arguments & Attributes Reference
created_at(Read-Only) (String). The creation timestamp of the resource.description(Read-Only) (String). The resource description.dhcp_options(Read-Only) (List Of Object).domain_name.domain_name_servers.ntp_servers.
folder_id(String). The folder identifier that resource belongs to. If it is not provided, the default providerfolder-idis used.id(String).labels(Read-Only) (Map Of String). A set of key/value label pairs which assigned to resource.name(String). The resource name.network_id(Read-Only) (String). ID of the network this subnet belongs to. Only networks that are in the distributed mode can have subnets.route_table_id(Read-Only) (String). The ID of the route table to assign to this subnet. Assigned route table should belong to the same network as this subnet.subnet_id(String). Subnet ID.v4_cidr_blocks(Read-Only) (List Of String). A list of blocks of internal IPv4 addresses that are owned by this subnet. Provide this property when you create the subnet. For example,10.0.0.0/22or192.168.0.0/16. Blocks of addresses must be unique and non-overlapping within a network. Minimum subnet size is/28, and maximum subnet size is/16. Only IPv4 is supported.v6_cidr_blocks(Read-Only) (List Of String). An optional list of blocks of IPv6 addresses that are owned by this subnet.zone(Read-Only) (String). The availability zone where resource is located. If it is not provided, the default provider zone will be used.