[Yandex Cloud documentation](../../../index.md) > [Yandex Compute Cloud](../../index.md) > [Step-by-step guides](../index.md) > Creating a disk > Creating a high-performance SSD

# Creating an ultra high-speed network storage with three replicas (SSD)


You can create an [ultra high-speed network storage](../../concepts/disk.md#nr-disks) with three replicas (SSD), which is a high-performance SSD offering the same speed as a non-replicated SSD, plus redundancy.

The disk size must be a multiple of 93 GB.

{% list tabs group=instructions %}

- Management console {#console}
  
  1. In the [management console](https://console.yandex.cloud), select the folder where you want to create a disk.
  1. Navigate to **Compute Cloud**.
  1. In the left-hand panel, select ![image](../../../_assets/console-icons/hard-drive.svg) **Disks**.
  1. Click **Create disk**.
  1. Enter a name for the disk. The naming requirements are as follows:
  
      * Length: between 3 and 63 characters.
      * It can only contain lowercase Latin letters, numbers, and hyphens.
      * It must start with a letter and cannot end with a hyphen.
  
  1. Add a description for the disk, if required.
  1. Select the [availability zone](../../../overview/concepts/geo-scope.md) the disk will reside in.
  1. Select `SSD IO` as the disk type.
  1. Select the required block size.
  1. Specify the required disk size.

  1. Optionally, under **Encryption**:
     
       * Select **Encrypted disk**.
       * In the **KMS key** field, select the [key](../../../kms/concepts/key.md) you created earlier. To [create](../../../kms/operations/key.md#create) a new key, click **Create**.
     
       To create an encrypted disk, you need the `kms.keys.user` [role](../../../kms/security/index.md#kms-keys-user) or higher.
     
       {% note warning %}
       
       You can specify encryption settings only when creating a disk. You cannot disable or change disk encryption. You also cannot enable encryption for an existing disk.
       
       {% endnote %}
       
       If you deactivate the key used to encrypt a disk, image, or snapshot, access to the data will be suspended until you reactivate the key.
       
       {% note alert %}
       
       If you destroy the key or its [version](../../../kms/concepts/version.md) used to encrypt a disk, image, or snapshot, you will irrevocably lose access to the data. For details, see [Destroying key version](../../../kms/concepts/version.md#version-distruct).
       
       {% endnote %}
  1. Click **Create disk**.

- CLI {#cli}
  
  The folder used by default is the one specified when [creating](../../../cli/operations/profile/profile-create.md) the CLI profile. To change the default folder, use the `yc config set folder-id <folder_ID>` command. You can also specify a different folder for any command using `--folder-name` or `--folder-id`. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.
  
  1. See the description of the CLI command for creating disks:
  
      ```bash
      yc compute disk create --help
      ```
  
  1. To create a high-performance disk named `ssd-io-disk`, run this command:

      ```bash
      yc compute disk create \
        --name ssd-io-disk \
        --zone ru-central1-a \
        --type network-ssd-io-m3 \
        --size 93G \
        --kms-key-id <key_ID>
      ```

      Where:

      * `--name`: Disk name.
      * `--zone`: Availability zone.
      * `--type`: Disk type.
      * `--size`: Disk size.
      * `--kms-key-id`: ID of the [KMS symmetric key](../../../kms/concepts/key.md) to create an encrypted disk. This is an optional setting.

        To create an encrypted disk, you need the `kms.keys.user` [role](../../../kms/security/index.md#kms-keys-user) or higher.
        
        {% note warning %}
        
        You can specify encryption settings only when creating a disk. You cannot disable or change disk encryption. You also cannot enable encryption for an existing disk.
        
        {% endnote %}

        If you deactivate the key used to encrypt a disk, image, or snapshot, access to the data will be suspended until you reactivate the key.
        
        {% note alert %}
        
        If you destroy the key or its [version](../../../kms/concepts/version.md) used to encrypt a disk, image, or snapshot, you will irrevocably lose access to the data. For details, see [Destroying key version](../../../kms/concepts/version.md#version-distruct).
        
        {% endnote %}

      Result:

      ```text
      id: a7li08c1fd8l********
      folder_id: aoerb349fdhb********
      created_at: "2024-11-25T21:22:20Z"
      name: ssd-io-disk
      type_id: network-ssd-io-m3
      zone_id: ru-central1-a
      size: "99857989632"
      block_size: "4096"
      status: READY
      disk_placement_policy: {}
      hardware_generation:
        legacy_features:
          pci_topology: PCI_TOPOLOGY_V1
      kms_key:
        key_id: abjbaqdga6hs********
        version_id: abj295dgqnlp********
      ```

- Terraform {#tf}

  With [Terraform](https://www.terraform.io/), 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](https://github.com/hashicorp/terraform/blob/main/LICENSE). The [Yandex Cloud provider for Terraform](https://github.com/yandex-cloud/terraform-provider-yandex) is distributed under the [MPL-2.0](https://www.mozilla.org/en-US/MPL/2.0/) license.
  
  For more information about the provider resources, see the guides on the [Terraform](https://www.terraform.io/docs/providers/yandex/index.html) website or [its mirror](../../../terraform/index.md).

  If you do not have Terraform yet, [install it and configure the Yandex Cloud provider](../../../tutorials/infrastructure-management/terraform-quickstart.md#install-terraform).
  
  
  To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), [authenticate](../../../terraform/authentication.md) using the appropriate method.

  To create a high-performance disk, do the following:
  1. In the Terraform configuration file, describe the resources you want to create:

     ```hcl
     resource "yandex_compute_disk" "empty-fast-disk" {
       name       = "<disk_name>"
       type       = "network-ssd-io-m3"
       zone       = "<availability_zone>"
       size       = 93
       block_size = 4096
       kms_key_id = <key_ID>
     }
     ```

     Where:
     * `name`: Disk name. The name format is as follows:

         * Length: between 3 and 63 characters.
         * It can only contain lowercase Latin letters, numbers, and hyphens.
         * It must start with a letter and cannot end with a hyphen.

     * `type`: Disk type, `ssd-io-m3`.
     * `zone`: [Availability zone](../../../overview/concepts/geo-scope.md). The availability zone for your disk must match the zone of the placement group where you want to create it. We recommend creating disks in the `ru-central1-a` or `ru-central1-b` availability zone.
     * `size`: Disk size in GB. This must be a multiple of 93 GB. The maximum disk size depends on the specified block size.
     * `block_size`: Block size in bytes (minimum storage unit on the disk). By default, the block size is 4 KB for all new disks; however, this is insufficient for disks larger than 8 TB. For more information, see [Creating an empty disk with a large block](empty-disk-blocksize.md).
     * `kms_key_id`: ID of the [KMS symmetric key](../../../kms/concepts/key.md) to create an [encrypted](../../concepts/encryption.md) disk. This is an optional setting.

         To create an encrypted disk, you need the `kms.keys.user` [role](../../../kms/security/index.md#kms-keys-user) or higher.

         {% note warning %}
         
         You can specify encryption settings only when creating a disk. You cannot disable or change disk encryption. You also cannot enable encryption for an existing disk.
         
         {% endnote %}

         If you deactivate the key used to encrypt a disk, image, or snapshot, access to the data will be suspended until you reactivate the key.
         
         {% note alert %}
         
         If you destroy the key or its [version](../../../kms/concepts/version.md) used to encrypt a disk, image, or snapshot, you will irrevocably lose access to the data. For details, see [Destroying key version](../../../kms/concepts/version.md#version-distruct).
         
         {% endnote %}

     For more information about `yandex_compute_disk`, see [this provider guide](../../../terraform/resources/compute_disk.md).

  1. Create the resources:

     1. In the terminal, navigate to the configuration file directory.
     1. Make sure the configuration is correct using this command:
     
        ```bash
        terraform validate
        ```
     
        If the configuration is valid, you will get this message:
     
        ```bash
        Success! The configuration is valid.
        ```
     
     1. Run this command:
     
        ```bash
        terraform plan
        ```
     
        You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration.
     1. Apply the configuration changes:
     
        ```bash
        terraform apply
        ```
     
     1. Type `yes` and press **Enter** to confirm the changes.

     Terraform will create all the required resources. You can check the new resources in the [management console](https://console.yandex.cloud) or using this [CLI](../../../cli/index.md) command:

     ```bash
     yc compute disk list
     ```

- API {#api}

  Use the [create](../../api-ref/Disk/create.md) REST API method for the [Disk](../../api-ref/Disk/index.md) resource or the [DiskService/Create](../../api-ref/grpc/Disk/create.md) gRPC API call.

{% endlist %}


#### Useful links {#see-also}

* [Creating a disk snapshot schedule](../snapshot-control/create-schedule.md)