Yandex Cloud
Поиск
Связаться с намиПодключиться
  • Истории успеха
  • Документация
  • Блог
  • Все сервисы
  • Статус работы сервисов
    • Популярные
    • Инфраструктура и сеть
    • Платформа данных
    • Контейнеры
    • Инструменты разработчика
    • Бессерверные вычисления
    • Безопасность
    • Мониторинг и управление ресурсами
    • ML Services
    • Бизнес-инструменты
  • Все решения
    • По отраслям
    • По типу задач
    • Экономика платформы
    • Безопасность
    • Техническая поддержка
    • Каталог партнёров
    • Обучение и сертификация
    • Облако для стартапов
    • Облако для крупного бизнеса
    • Центр технологий для общества
    • Облако для интеграторов
    • Поддержка IT-бизнеса
    • Облако для фрилансеров
    • Обучение и сертификация
    • Блог
    • Документация
    • Контент-программа
    • Мероприятия и вебинары
    • Контакты, чаты и сообщества
    • Идеи
    • Тарифы Yandex Cloud
    • Промоакции и free tier
    • Правила тарификации
  • Истории успеха
  • Документация
  • Блог
Проект Яндекса
© 2025 ООО «Яндекс.Облако»
Terraform в Yandex Cloud
  • Начало работы
  • Библиотека решений
    • История изменений (англ.)
          • 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

В этой статье:

  • Example usage
  • Schema
  • Optional
  • Read-Only
  • Nested Schema for hardware_generation
  • Nested Schema for hardware_generation.generation2_features
  • Nested Schema for hardware_generation.legacy_features
  • Nested Schema for timeouts
  • Import
  1. Справочник Terraform
  2. Ресурсы (англ.)
  3. Compute Cloud
  4. Resources
  5. compute_image

yandex_compute_image (Resource)

Статья создана
Yandex Cloud
Обновлена 11 сентября 2025 г.
  • Example usage
  • Schema
    • Optional
    • Read-Only
    • Nested Schema for hardware_generation
    • Nested Schema for hardware_generation.generation2_features
    • Nested Schema for hardware_generation.legacy_features
    • Nested Schema for timeouts
  • Import

Creates a virtual machine image resource for the Yandex Compute Cloud service from an existing tarball. For more information, see the official documentation.

Важно

One of source_family, source_image, source_snapshot, source_disk or source_url must be specified.

Example usageExample usage

//
// Create a new Compute Image.
//
resource "yandex_compute_image" "foo-image" {
  name       = "my-custom-image"
  source_url = "https://storage.yandexcloud.net/lucky-images/kube-it.img"
}

// You can use "data.yandex_compute_image.my_image.id" identifier 
// as reference to existing resource.
resource "yandex_compute_instance" "vm" {
  name = "vm-from-custom-image"

  # ...

  boot_disk {
    initialize_params {
      image_id = yandex_compute_image.foo-image.id
    }
  }
}

SchemaSchema

OptionalOptional

  • description (String) The resource description.
  • family (String) The name of the image family to which this image belongs.
  • folder_id (String) The folder identifier that resource belongs to. If it is not provided, the default provider folder-id is used.
  • hardware_generation (Block List, Max: 1) Hardware generation and its features, which will be applied to the instance when this image is used for creating a boot disk. Provide this property if you wish to override this value, which otherwise is inherited from the source. (see below for nested schema)
  • labels (Map of String) A set of key/value label pairs which assigned to resource.
  • min_disk_size (Number) Minimum size in GB of the disk that will be created from this image.
  • name (String) The resource name.
  • os_type (String) Operating system type that is contained in the image. Possible values: LINUX, WINDOWS.
  • pooled (Boolean) Optimize the image to create a disk.
  • product_ids (Set of String) License IDs that indicate which licenses are attached to this image.
  • source_disk (String) The ID of a disk to use as the source of the image. Changing this ID forces a new resource to be created.
  • source_family (String) The name of the family to use as the source of the new image. The ID of the latest image is taken from the standard-images folder. Changing the family forces a new resource to be created.
  • source_image (String) The ID of an existing image to use as the source of the image. Changing this ID forces a new resource to be created.
  • source_snapshot (String) The ID of a snapshot to use as the source of the image. Changing this ID forces a new resource to be created.
  • source_url (String) The URL to use as the source of the image. Changing this URL forces a new resource to be created.
  • timeouts (Block, Optional) (see below for nested schema)

Read-OnlyRead-Only

  • created_at (String) The creation timestamp of the resource.
  • id (String) The ID of this resource.
  • size (Number) The size of the image, specified in GB.
  • status (String) The status of the image.

Nested Schema for Nested Schema for hardware_generation

Optional:

  • 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

Nested Schema for Nested Schema for hardware_generation.legacy_features

Optional:

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

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).
  • 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.
  • 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_image.<resource Name> <resource Id>
terraform import yandex_compute_image.my_image fd8go**********trjsd

Была ли статья полезна?

Предыдущая
compute_gpu_cluster_iam_binding
Следующая
compute_image_iam_binding
Проект Яндекса
© 2025 ООО «Яндекс.Облако»