Encrypting an image

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

1. Create a Yandex Key Management Service encryption key:

   yc kms symmetric-key create \
     --name <key_name> \
     --default-algorithm aes-256 \
     --rotation-period 24h \
     --deletion-protection
   

   Where --name is the name of the new Key Management Service key.

   Result:

   id: abj73fd9mekk********
   folder_id: b1geoelk7fld********
   created_at: "2025-05-20T17:27:35Z"
   name: my-key1
   status: ACTIVE
   primary_version:
     id: abjdno4pqi67********
     key_id: abj73fd9mekk********
     status: ACTIVE
     algorithm: AES_256
     created_at: "2025-05-20T17:27:35Z"
     primary: true
   default_algorithm: AES_256
   rotation_period: 86400s
   deletion_protection: true
   

2. Get a list of all images in the default folder:

   yc compute image list
   

   Result:

   +----------------------+--------------------+------------------------+----------+
   |          ID          |        NAME        |       PRODUCT IDS      |  STATUS  |
   +----------------------+--------------------+------------------------+----------+
   | fd823vsvcmop******** | image-ubuntu-24-04 | igf2etq3erab3o******** | READY    |
   | fd8p8l3asgud******** | image-debian-2025  | goa2etq3erab3o******** | READY    |
   +----------------------+--------------------+------------------------+----------+
   

3. Create an encrypted disk from the image you want to encrypt:

   yc compute disk create <encrypted_disk_name> \
     --source-image-name <image_name> \
     --kms-key-name <key_name>
   

   Where:

   • --source-image-name: Image name to create an encrypted disk.
   • --kms-key-name: Encryption key name.

   Result:

   done (53s)
   id: fhmihpagi991********
   folder_id: b1geoelk7fld********
   created_at: "2025-05-20T17:39:01Z"
   name: fromcliencrypted
   type_id: network-hdd
   zone_id: ru-central1-a
   size: "21474836480"
   block_size: "4096"
   status: READY
   source_image_id: sd1lb3jnrcs2********
   disk_placement_policy: {}
   hardware_generation:
     legacy_features:
       pci_topology: PCI_TOPOLOGY_V1
   kms_key:
     key_id: abj73fd9mekk********
     version_id: abjdno4pqi67********
   

   Once created, the disk will get the Creating status. Wait until the disk status changes to Ready before using it.

4. Get a list of all disks in the default folder:

   yc compute disk list
   

   Result:

   +----------------------+--------------+-------------+---------------+--------+----------------------+-------------------------+
   |          ID          |     NAME     |    SIZE     |     ZONE      | STATUS |     INSTANCE IDS     |       DESCRIPTION       |
   +----------------------+--------------+-------------+---------------+--------+----------------------+-------------------------+
   | a7lqgbt0bb9s******** | first-disk   | 20401094656 | ru-central1-a | READY  | a7lcvu28njbh******** |                         |
   | a7lv5j5hm1p1******** | second-disk  | 21474836480 | ru-central1-a | READY  |                      |                         |
   +----------------------+--------------+-------------+---------------+--------+----------------------+-------------------------+
   

5. Create an image from the encrypted disk you created earlier:

   yc compute image create \
     --name <name_of_new_image> \
     --source-disk-name <encrypted_disk_name>
   

   Result:

   done (8s)
   id: fd87fubin9ql********
   folder_id: b1geoelk7fld********
   created_at: "2025-06-25T10:52:31Z"
   name: encrypted-image
   min_disk_size: "5368709120"
   status: READY
   os:
     type: LINUX
   hardware_generation:
     legacy_features:
       pci_topology: PCI_TOPOLOGY_V1
   kms_key:
     key_id: abjgkrgibtmo********
     version_id: abjvf41ltfi8********
   

6. Delete the encrypted disk:

   yc compute disk delete <encrypted_disk_name>
   

   Result:

   done (4s)
   

7. Delete the source image:

   yc compute image delete <unencrypted_image_name>
   

   Result:

   done (2s)
   

With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

Terraform is distributed under the Business Source License. The Yandex Cloud provider for Terraform is distributed under the MPL-2.0 license.

For more information about the provider resources, see the relevant documentation on the Terraform website or its mirror.

If you do not have Terraform yet, install it and configure the Yandex Cloud provider.

To encrypt an image using Terraform:

1. In the Terraform configuration file, describe the resources you want to create:

   # Creating a Yandex Key Management Service key
   
   resource "yandex_kms_symmetric_key" "my-key" {
     name                = "encrypt-key"
     default_algorithm   = "AES_256"
     rotation_period     = "8760h"
     deletion_protection = true
     lifecycle {
       prevent_destroy = true
     }
   }
   
   # Creating an encrypted disk
   
   resource "yandex_compute_disk" "encrypted-disk" {
     name       = "new-encrypted-disk"
     type       = "network-hdd"
     zone       = "ru-central1-a"
     size       = 20
     block_size = 4096
     image_id   = "<unencrypted_image_ID>"
     kms_key_id = yandex_kms_symmetric_key.my-key.id
   }
   
   # Creating an encrypted image
   
   resource "yandex_compute_image" "encrypted-image" {
     name           = "<encrypted_image_name>"
     source_disk_id = yandex_compute_disk.encrypted-disk.id
     depends_on     = [yandex_compute_disk.encrypted-disk]
   }
   

   Where:

   • image_id: Unencrypted image ID.
   • name: Name of the new encrypted image.

   For more information about yandex_compute_snapshot properties, see the relevant provider documentation.

2. Create the resources:

   1. In the terminal, navigate to the directory where you edited the configuration file.

   2. Make sure the configuration file is correct using this command:

      terraform validate
      

      If the configuration is correct, you will get this message:

      Success! The configuration is valid.
      

   3. Run this command:

      terraform plan
      

      You will see a detailed list of resources. No changes will be made at this step. If the configuration contains any errors, Terraform will show them.

   4. Apply the changes:

      terraform apply
      

   5. Type yes and press Enter to confirm the changes.

   Once created, the disk will get the Creating status. Wait until the disk status changes to Ready before using it.

3. Delete the encrypted disk.

4. Delete the source image.

1. Create a Yandex Key Management Service encryption key using the create REST API method for the SymmetricKey resource or the SymmetricKeyService/Create gRPC API call.

2. Create an encrypted disk from an image using the create REST API method for the Disk resource or the DiskService/Create gRPC API call.

   To request a list of available images, use the list REST API method or the ImageService/List gRPC API call.

   Once created, the disk will get the Creating status. Wait until the disk status changes to Ready before using it.

3. For the encrypted disk, create an image using the create REST API method for the Image resource or the ImageService/Create gRPC API call.

4. Delete the encrypted disk using the delete REST API method for the Disk resource or the DiskService/Delete gRPC API call.

5. Delete the source image using the delete REST API method for the Image resource or the ImageService/Delete gRPC API call.