Yandex Cloud
Search
Contact UsTry it for free
  • 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
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Terraform in Yandex Cloud
  • Getting started
  • Solution library
    • Overview
    • Release notes
          • compute_disk
          • compute_disk_placement_group
          • compute_filesystem
          • compute_gpu_cluster
          • compute_image
          • compute_instance
          • compute_instance_group
          • compute_placement_group
          • compute_snapshot
          • compute_snapshot_schedule

In this article:

  • Example usage
  • Schema
  • Optional
  • Read-Only
  • Nested Schema for disk_placement_policy
  • Nested Schema for hardware_generation
  • Nested Schema for hardware_generation.generation2_features
  • Nested Schema for hardware_generation.legacy_features
  1. Terraform reference
  2. Resources
  3. Compute Cloud
  4. Data Sources
  5. compute_disk

yandex_compute_disk (Data Source)

Written by
Yandex Cloud
Updated at September 11, 2025
  • Example usage
  • Schema
    • Optional
    • Read-Only
    • Nested Schema for disk_placement_policy
    • Nested Schema for hardware_generation
    • Nested Schema for hardware_generation.generation2_features
    • Nested Schema for hardware_generation.legacy_features

Get information about a Yandex Compute disk. For more information, see the official documentation.

Warning

One of disk_id or name should be specified.

Example usageExample usage

//
// Get information about existing Compute Disk.
//
data "yandex_compute_disk" "my_disk" {
  disk_id = "some_disk_id"
}

// You can use "data.yandex_compute_disk.my_disk.id" identifier 
// as reference to the existing resource.
resource "yandex_compute_instance" "default" {
  # ...

  secondary_disk {
    disk_id = data.yandex_compute_disk.my_disk.id
  }
}

SchemaSchema

OptionalOptional

  • disk_id (String) The ID of a specific disk.
  • disk_placement_policy (Block List, Max: 1) (see below for nested schema)
  • 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.

Read-OnlyRead-Only

  • block_size (Number) Block size of the disk, specified in bytes.
  • created_at (String) The creation timestamp of the resource.
  • description (String) The resource description.
  • hardware_generation (List of Object) (see below for nested schema)
  • id (String) The ID of this resource.
  • image_id (String) The source image to use for disk creation.
  • instance_ids (List of String)
  • kms_key_id (String) ID of KMS symmetric key used to encrypt disk.
  • labels (Map of String) A set of key/value label pairs which assigned to resource.
  • product_ids (List of String)
  • size (Number) Size of the persistent disk, specified in GB. You can specify this field when creating a persistent disk using the image_id or snapshot_id parameter, or specify it alone to create an empty persistent disk. If you specify this field along with image_id or snapshot_id, the size value must not be less than the size of the source image or the size of the snapshot.
  • snapshot_id (String) The source snapshot to use for disk creation.
  • status (String) The status of the disk.
  • type (String) Type of disk to create. Provide this when creating a disk.
  • zone (String) The availability zone where resource is located. If it is not provided, the default provider zone will be used.

Nested Schema for Nested Schema for disk_placement_policy

Required:

  • disk_placement_group_id (String) Specifies Disk Placement Group id.

Nested Schema for Nested Schema for hardware_generation

Read-Only:

  • generation2_features (Block List, Max: 1) A newer hardware generation, which always uses PCI_TOPOLOGY_V2 and UEFI boot. (see below for nested schema)

  • legacy_features (Block List, Max: 1) Defines the first known hardware generation and its features. (see below for nested schema)

Nested Schema for Nested Schema for hardware_generation.generation2_features

Read-Only:

Nested Schema for Nested Schema for hardware_generation.legacy_features

Read-Only:

  • pci_topology (String) A variant of PCI topology, one of PCI_TOPOLOGY_V1 or PCI_TOPOLOGY_V2.

Was the article helpful?

Previous
cloudregistry_registry_ip_permission
Next
compute_disk_placement_group
© 2025 Direct Cursus Technology L.L.C.