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_iam_binding
          • compute_disk_placement_group
          • compute_disk_placement_group_iam_binding
          • compute_filesystem
          • compute_filesystem_iam_binding
          • compute_gpu_cluster
          • compute_gpu_cluster_iam_binding
          • compute_image
          • compute_image_iam_binding
          • compute_instance
          • compute_instance_group
          • compute_instance_iam_binding
          • compute_placement_group
          • compute_placement_group_iam_binding
          • compute_snapshot
          • compute_snapshot_iam_binding
          • compute_snapshot_schedule
          • compute_snapshot_schedule_iam_binding

In this article:

  • Example usage
  • Schema
  • Optional
  • Read-Only
  • Nested Schema for timeouts
  • Import
  1. Terraform reference
  2. Resources
  3. Compute Cloud
  4. Resources
  5. compute_filesystem

yandex_compute_filesystem (Resource)

Written by
Yandex Cloud
Updated at October 2, 2025
  • Example usage
  • Schema
    • Optional
    • Read-Only
    • Nested Schema for timeouts
  • Import

A filesystem resource.
For details about the concept, see documentation.

Example usageExample usage

//
// Create a new Compute Filesystem.
//
resource "yandex_compute_filesystem" "default" {
  name = "fs-name"
  type = "network-ssd"
  zone = "ru-central1-a"
  size = 10

  labels = {
    environment = "test"
  }
}

SchemaSchema

OptionalOptional

  • block_size (Number) Block size used for the filesystem, specified in bytes.
  • description (String) Description of the filesystem.
  • filesystem_id (String) ID of the filesystem to return.

To get the filesystem ID, make a [FilesystemService.List] request.

  • folder_id (String) ID of the folder that the filesystem belongs to.
  • id (String) ID of the filesystem to return.

To get the filesystem ID, make a [FilesystemService.List] request.

  • labels (Map of String) Filesystem labels as key:value pairs.
    For details about the concept, see documentation.
  • name (String) Name of the filesystem. The name is unique within the folder.
  • size (Number) Size of the filesystem, specified in bytes.
  • timeouts (Block, Optional) (see below for nested schema)
  • type (String) ID of the filesystem type.

To get a list of available filesystem types, make a [yandex.cloud.compute.v1.DiskTypeService.List] request.

  • zone (String) ID of the availability zone where the filesystem resides.

A filesystem can be attached only to instances residing in the same availability zone.

Read-OnlyRead-Only

  • created_at (String) Creation timestamp.
  • status (String) Current status of the filesystem.

Nested Schema for Nested Schema for timeouts

Optional:

  • create (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
  • delete (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
  • read (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Read operations occur during any refresh or planning operation when refresh is enabled.
  • update (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).

ImportImport

The resource can be imported by using their resource ID. For getting the resource ID you can use Yandex Cloud Web Console or YC CLI.

# terraform import yandex_compute_filesystem.<resource Name> <resource Id>
terraform import yandex_compute_filesystem.my_filesystem fhmc7**********ngipq

Was the article helpful?

Previous
compute_disk_placement_group_iam_binding
Next
compute_filesystem_iam_binding
© 2025 Direct Cursus Technology L.L.C.