# Leasing a stock configuration server

You can lease a [BareMetal server](../../concepts/servers.md) in one of the [stock configurations](../../concepts/server-configurations.md#standard).

However, if you need a server with some non-standard hardware specifications, you can [configure](custom-server-lease.md) one yourself.

To lease a server in a stock configuration:

{% list tabs group=instructions %}

- Management console {#console}

  1. In the [management console](https://console.yandex.cloud), select the [folder](../../../resource-manager/concepts/resources-hierarchy.md#folder) where you want to lease a server.
  1. Navigate to **BareMetal**.
  1. Click **Lease server** and in the window that opens, select `Stock configurations` and a suitable BareMetal server [configuration](../../concepts/server-configurations.md).
     
     To select the suitable server configuration, click the section with its name in the central part of the screen.
     
     {% note info %}
     
     To quickly find the right configuration, you can use the filter with the hardware characteristics of the configurations on the right side of the screen.
     
     {% endnote %}
     
     {% note tip %}
     
     You can reduce the cost of renting a server in some configurations by ordering server [assembly](../../concepts/server-custom-configurations.md#assembly).
     
     To use the discount, hover over **Cheaper with assembly** ![circle-info.svg](../../../_assets/console-icons/circle-info.svg) under the configuration at hand and click ![person-nut-hex.svg](../../../_assets/console-icons/person-nut-hex.svg) **Go to assembly** in the pop-up window.
     
     When ordering a server with assembly, follow the steps below to configure the server properties. In this case, the server will not be available immediately, but only after the assembly is completed (within four calendar days), and at a lower price.
     
     {% endnote %}
  1. In the server configuration window that opens, do the following:

      1. Under **Configuration**, **Location**, and **Lease conditions**, make sure the server configuration you have provided so far is adequate.
         
         If not, click ![arrow-left](../../../_assets/console-icons/arrow-left.svg) under **Configuration** to return to configuration setup.
      1. In the **Lease duration** field, select the [lease period](../../concepts/servers.md#server-lease): `1 day`, `1 month`, `3 months`, `6 months`, or `1 year`.
         
         When this period expires, server lease will automatically be renewed for the same period. You cannot terminate the lease during the specified lease period, but you can [refuse](server-lease-cancel.md) to extend the server lease further.
      1. In the **Number of servers** field, select how many servers of this configuration that you want to lease.
      1. Under **Image**, select:
         
         * `Marketplace`: To install one of the available Yandex Cloud Marketplace [public OS images](../../concepts/images.md#marketplace-images) on the server.
         * `No OS`: To lease a server without an operating system.
         
             You can [install](reinstall-os-from-own-image.md) the OS from a [custom ISO image](../../concepts/images.md#user-images) later.
      1. Optionally, under **Disk**, configure [disk](../../concepts/disks/disk-types.md) partitioning:
         
         1. Click **Configure disk layout**.
         1. Specify partition settings. To create a new partition, click ![icon](../../../_assets/console-icons/plus.svg) **Add partition**.
         
             To configure [RAID](../../concepts/disks/raid.md) arrays and disk partitions by yourself, click **Remove RAID**.
         1. Click **Save**.
      1. Under **Network interfaces**, in the **Interface 1** section, select a [private subnet](../../concepts/private-network.md#private-subnet) in the [availability zone](../../../overview/concepts/geo-scope.md) you are renting the server in.
         
         If the server’s availability zone does not have a private subnet yet, or you want to create a new private subnet, click **Create** and, in the window that opens, specify subnet settings as described in [Creating a private subnet](../subnet-create.md).
      1. Under **Network interfaces**, in the **Interface 2** section:
         
         * In the **Public address** field, select a public IP address assignment method:
         
             * `From ephemeral subnet`: Assign a random IP address. If you need to get the IP address when creating a server via a request to a DHCP server, enable **Assign via DHCP**.
         
             * `From a dedicated subnet`: To assign an IP address from the range of addresses of a [dedicated public subnet](../../concepts/public-network.md#public-subnet).
             
                 In the field that opens, select a public subnet or click **Order** to [order](../reserve-public-subnet.md) a new one.
             
                 {% note warning %}
             
                 The dedicated public subnet [does not have](../../concepts/dhcp.md#dhcp-public-subnet) a DHCP server; therefore, on the network interface of the server connected to such subnet, you should manually configure a static IP address from the subnet’s range of available public IP addresses and specify the default gateway address.
             
                 {% endnote %}
         
             * `No address`: Do not assign a public IP address.
         
         * In the **Bandwidth** field, select a [server bandwidth](../../concepts/network-restrictions.md#bandwidth-for-pubic-network) package. Available bandwidth packages:
           
           * `10 TB per day, connection capacity, 1 Gbit/s`
           * `100 TB per day, connection capacity, 10 Gbit/s`
           
           {% note info %}
           
           You can select a bandwidth package only for configurations with a public IP address and network cards of 10 Gbps or higher.
           
           You can reduce the connection capacity to 10 TB per day only as early as 24 hours after the server lease starts.
           
           {% endnote %}
      1. If you are installing an OS from a Marketplace public image, specify server access settings under **Access**:

          1. In the **Password** field, select one of the following options to create a root password:
          
              * To generate a new root password, select `New password` and click **Generate**.
          
                  {% note warning %}
                  
                  This option requires you to maintain password security. Save the password you generated in a secure location. Yandex Cloud does not store it, and you will not be able to retrieve it once the server is deployed.
                  
                  {% endnote %}
          
              * To use the root password saved in a Yandex Lockbox [secret](../../../lockbox/concepts/secret.md), select `Lockbox secret`.
          
                  In the **Name**, **Version**, and **Key** fields, select the secret containing your password, its version, and its key, respectively.
                  
                  If you do not have a Yandex Lockbox secret, click **Create** to create it.
          
                  Choose the `Custom` secret type to specify a custom password or `Generated` to generate password automatically.
          
          1. In the **Public SSH key** field, select the SSH key saved in your [organization user](../../../organization/concepts/membership.md) profile.
          
              If there are no SSH keys in your profile or you want to add a new key:
              
              1. Click **Add key**.
              1. Enter a name for the SSH key.
              1. Select one of the following:
              
                  * `Enter manually`: Paste the contents of the public SSH key. You need to [create](../../../compute/operations/vm-connect/ssh.md#creating-ssh-keys) an SSH key pair on your own.
                  * `Load from file`: Upload the public part of the SSH key. You need to create an SSH key pair on your own.
                  * `Generate key`: Automatically create an SSH key pair.
                  
                    When adding a new SSH key, an archive containing the key pair will be created and downloaded. In Linux or macOS-based operating systems, unpack the archive to the `/home/<user_name>/.ssh` directory. In Windows, unpack the archive to the `C:\Users\<user_name>/.ssh` directory. You do not need additionally enter the public key in the management console.
              
              1. Click **Add**.
              
              The system will add the SSH key to your organization user profile. If the organization has [disabled](../../../organization/operations/os-login-access.md) the ability for users to add SSH keys to their profiles, the added public SSH key will only be saved in the user profile inside the newly created resource.

      1. Optionally, enable server backup in [Yandex Cloud Backup](../../../backup/index.md):

          1. Enable **Backup**.
          1. Select an existing [backup policy](../../../backup/concepts/policy.md) or [create](../../../backup/operations/policy-vm/create.md) a new one.
          1. Select a [service account](../../../iam/concepts/users/service-accounts.md) with the [`baremetal.editor`](../../security/index.md#baremetal-editor) and [`backup.user`](../../../backup/security/index.md#backup-user) roles assigned or [create](../../../iam/operations/sa/create.md) a new one.

          For more information, see [Leasing a Yandex BareMetal server connected to Cloud Backup](../../../backup/operations/backup-baremetal/lease-server-with-backup.md).
      1. Under **Server information**:
         
           1. Specify the server name in the **Name** field. Follow these naming requirements:
         
               * 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. Optionally, add a server description in the **Description** field.
           1. Optionally, set [labels](../../../resource-manager/concepts/labels.md) in the **Labels** field.
      1. Click **Lease server**.

- CLI {#cli}

  If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../../cli/quickstart.md#install).

  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. View the description of the command for leasing a server:
     
     ```bash
     yc baremetal server create --help
     ```
  1. Get a list of configurations:
     
     ```bash
     yc baremetal configuration list
     ```
     
     Approximate result:
     
     ```text
     +----------------------+---------------------+-----------+--------------------------------+--------------------------------+-------------------------+---------+
     |          ID          |        NAME         | MEMORYGIB |              CPU               |          DISK DRIVES           | NETWORK BMANDWIDTH GBPS | CPU NUM |
     +----------------------+---------------------+-----------+--------------------------------+--------------------------------+-------------------------+---------+
     | ly577w5sepew******** | LA-i108-S-1/10G     |        32 | physical cores: 4, mhz: 2400,  | [ type: SSD count: 2 size_gib: |                      10 |       1 |
     |                      |                     |           | name: Xeon D-1521, vendor:     | 838 ]                          |                         |         |
     |                      |                     |           | Intel                          |                                |                         |         |
     | ly5tdlrmwezt******** | LA-i107-S-1/10G     |        16 | physical cores: 4, mhz: 2400,  | [ type: SSD count: 2 size_gib: |                      10 |       1 |
     |                      |                     |           | name: Xeon D-1521, vendor:     | 838 ]                          |                         |         |
     |                      |                     |           | Intel                          |                                |                         |         |
     | ly527jeaz2nb******** | BA-i202-S           |       128 | physical cores: 8, mhz: 2600,  | [ type: SSD count: 2 size_gib: |                       1 |       2 |
     |                      |                     |           | name: Xeon E5-2650V2, vendor:  | 838 ]                          |                         |         |
     |                      |                     |           | Intel                          |                                |                         |         |
     ...
     ...
     | ly52arjxxbl3******** | LA-i114-S           |        64 | physical cores: 8, mhz: 2200,  | [ type: SSD count: 2 size_gib: |                       1 |       2 |
     |                      |                     |           | name: Xeon E5-2660, vendor:    | 838 ]                          |                         |         |
     |                      |                     |           | Intel                          |                                |                         |         |
     +----------------------+---------------------+-----------+--------------------------------+--------------------------------+-------------------------+---------+
     ```
  1. Get detailed info about a configuration by stating its ID or name:

      ```bash
      yc baremetal configuration get <configuration_ID_or_name>
      ```

      Result:
      
      ```yaml
      id: ly5tdlrmwezt********
      name: LA-i107-S-1/10G
      memory_gib: "16"
      cpu:
        name: Xeon D-1521
        vendor: Intel
        cores: "8"
        physical_cores: "4"
        frequency_mhz: "2400"
      disk_drives:
        - type: SSD
          disk_count: "2"
          disk_size_gib: "838"
      network_capacity_gbps: "10"
      cpu_num: "1"
      network_interfaces:
      - id: ly5oc5p4u6vg********
        name: iface0
        configuration_id: ly5tdlrmwezt********
        link_speed_gbps: '1'
        available_modes:
        - PRIVATE
      - id: ly5dmh2u3qwe********
        name: iface1
        configuration_id: ly5tdlrmwezt********
        link_speed_gbps: '1'
        available_modes:
        - PUBLIC
        - PRIVATE
      ```

  1. Lease a server:
     
     ```bash
     yc baremetal server create \
       --hardware-pool-id <pool> \
       --configuration-id <configuration_ID> \
       --storage "partition={type=<file_system>,size-gib=<partition_size>,mount-point=<mount_point>},raid-type=<RAID array level>,disk={id=<disk_number>,size-gib=<disk_size>,type=<disk_type>}" \
       --os-settings "image-id=<image_ID>,image-name=<image_name>,ssh-key-public=<public_SSH_key_contents>,ssh-key-user-id=<SSH_key_user_ID>,password-plain-text=<user_password>,password-lockbox-secret={secret-id=<secret_ID>,version-id=<secret_version>,key=<secret_key>}" \
       --rental-period-id <lease_period> \
       --network-interfaces private-subnet-id=<private_subnet_ID> \
       --network-interfaces public-subnet-id=<public_subnet_ID> \
       --name <server_name> \
       --description "<server_description>" \
       --labels <label_key>=<label_value>
     ```

      Where:
      * `--hardware-pool-id`: [Pool](../../concepts/servers.md#server-pools) to lease a server from.
      * `--configuration-id`: [Server configuration](../../concepts/server-configurations.md) ID.
      * `--storage`: [Disk](../../concepts/disks/disk-types.md) partitioning settings. This is an optional setting. Possible settings:
        
        * `partition`: Disk partition:
          
          * `type`: File system. The possible values are `Ext3`, `Ext4`, `Swap`, or `Xfs`.
          * `size-gib`: Partition size in GB.
          * `mount-point`: Mount point.
        
        * `disk`: Disk:
          
          * `id`: Disk number.
          * `size-gib`: Disk size in GB.
          * `type`: Disk type.
        * `raid-type`: [RAID array level](../../concepts/disks/raid.md#levels).
      * `--os-settings`: OS settings. To lease a server without an operating system, skip this parameter. Possible settings:
        
        * `image-id`: ID of an available Yandex Cloud Marketplace public OS [image](../../concepts/images.md#marketplace-images).
        * `image-name`: Name of one of the available Yandex Cloud Marketplace public OS images.
        * `ssh-key-public`: Public SSH key contents. You will need to [create](../../../compute/operations/vm-connect/ssh.md#creating-ssh-keys) your own SSH key pair to establish a secure server connection.
        * `ssh-key-user-id`: SSH key user ID.
        * `password-plain-text`: Root user's password.
        
          {% note warning %}
          
          This option requires you to maintain password security. Save the password you generated in a secure location. Yandex Cloud does not store it, and you will not be able to retrieve it once the server is deployed.
          
          {% endnote %}
        
        * `password-lockbox-secret`: Yandex Lockbox [secret](../../../lockbox/concepts/secret.md):
          * `secret-id`: Secret ID.
          * `version-id`: Secret version.
          * `key`: Secret key.

          You can [install](reinstall-os-from-own-image.md) the OS from a [custom ISO image](../../concepts/images.md#user-images) later.

      * `--rental-period-id`: Server lease period. The possible values are `1 day`, `1 month`, `3 months`, `6 months` or `1 year`.

          When this period expires, server lease will automatically be renewed for the same period. You cannot terminate the lease during the specified lease period, but you can [refuse](server-lease-cancel.md) to extend the server lease further.

      * `--network-interfaces`: Network settings:
        
        * `private-subnet-id`: [Private subnet](../../concepts/private-network.md#private-subnet) ID.
        * `public-subnet-id`: [Dedicated public subnet](../../concepts/public-network.md#public-subnet) ID. This is an optional parameter.

          {% note warning %}

          The dedicated public subnet [does not have](../../concepts/dhcp.md#dhcp-public-subnet) a DHCP server; therefore, on the network interface of the server connected to such subnet, you should manually configure a static IP address from the subnet’s range of available public IP addresses and specify the default gateway address.

          {% endnote %}

      * `--name`: Server name.
      * `--description`: Server description. This is an optional parameter.
      * `--labels`: Server labels. This is an optional parameter.

- API {#api}

  To rent a server, use the [create](../../api-ref/Server/create.md) REST API method for the [Server](../../api-ref/Server/index.md) resource or the [ServerService/Create](../../api-ref/grpc/Server/create.md) gRPC API call.

{% endlist %}

Once you lease a server, you can install or reinstall the OS at any time using either a Cloud Marketplace public image or your own custom ISO. For more information, see [Reinstalling an OS from a Marketplace image](reinstall-os-from-marketplace.md) and [Reinstalling an OS from a custom ISO image](reinstall-os-from-own-image.md).

## Example {#example}

Lease a server with a public OS image:

{% list tabs group=instructions %}

- CLI {#cli}

  ```bash
  yc baremetal server create \
    --hardware-pool-id ru-central1-m4 \
    --configuration-id ly5lymxdltk3******** \
    --storage "partition={type=EXT3,size-gib=1000,mount-point=/},partition={type=EXT4,size-gib=500,mount-point=/root},raid-type=RAID0,disk={id=1,size-gib=1862,type=HDD},disk={id=2,size-gib=1862,type=HDD}" \
    --storage "partition={type=EXT3,size-gib=1000,mount-point=/boot},partition={type=SWAP,size-gib=10},disk={id=3,size-gib=1862,type=HDD}" \
    --os-settings "image-id=ly5vhn4lapev********,ssh-key-public=ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIGcM4tRfRHJGrlLMT+YJFr+aOdSQYnYYjAoj********,password-lockbox-secret={secret-id=e6qmvglkitn6********,version-id=e6qquvv4kh8e********,key=password}" \
    --rental-period-id 1-day \
    --network-interfaces private-subnet-id=ly5ztavbezrf******** \
    --network-interfaces public-subnet-id=ly5o6l7pxmk2********* \
    --name demo-baremetal-server \
    --description "My first BareMetal server" \
    --labels env=test
  ```

  Result:
  
  ```text
  done (22m45s)
  id: ly52dtzdi55r********
  cloud_id: b1gia87mbaom********
  folder_id: b1g0ijbfaqsn********
  name: demo-baremetal-server
  description: My first BareMetal server
  zone_id: ru-central1-m
  hardware_pool_id: ru-central1-m4
  status: PROVISIONING
  os_settings:
    image_id: ly5vhn4lapev********
    ssh_public_key: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIGcM4tRfRHJGrlLMT+YJFr+aOdSQYnYYjAoj********
    storages:
      - partitions:
          - type: EXT3
            size_gib: "999"
            mount_point: /
          - type: EXT4
            size_gib: "499"
            mount_point: /root
        raid:
          type: RAID0
          disks:
            - id: ly5ual3jbnhr********
              type: HDD
              size_gib: "1862"
            - id: ly54qfjw55d4********
              type: HDD
              size_gib: "1862"
      - partitions:
          - type: EXT3
            size_gib: "999"
            mount_point: /boot
          - type: SWAP
            size_gib: "9"
        disk:
          id: ly5ojffpngul********
          type: HDD
          size_gib: "1862"
  network_interfaces:
    - id: ly5wbsiklrtd********
      mac_address: 00:25:90:92:fa:48
      private_subnet:
        private_subnet_id: ly5ztavbezrf********
    - id: ly5ygl4loyy6********
      mac_address: 00:25:90:92:fa:49
      public_subnet:
        public_subnet_id: ly5o6l7pxmk2********
  configuration_id: ly5lymxdltk3xitpkrmi
  created_at: "2025-07-06T21:53:46.186130Z"
  labels:
    env: test
  ```

- API {#api}

  ```bash
  curl -X POST \
   -H "Content-Type: application/json" \
   -H "Authorization: Bearer <IAM_token>" \
   -d '{
     "folderId": "b1g07hj5r6i4********",
     "name": "bm-test-server",
     "description": "New Test Baremetal Server",
     "hardwarePoolId": "ru-central1-m3",
     "configurationId": "ly5fcdnlzp7j********",
     "rentalPeriodId": "1-day",
     "networkInterfaces": [
       {
         "privateSubnet": {
           "privateSubnetId": "ly52xefxa2hi********"
         }
       },
       {
         "publicSubnet": {
           "publicSubnetId": "ly52yjugkj57********"
         }
       }
     ],
     "osSettingsSpec": {
       "imageId": "ly5vyzcggvci********",
       "storages": [
         {
           "partitions": [
             {
               "type": "EXT3",
               "sizeGib": "9",
               "mountPoint": "/boot"
             },
             {
               "type": "SWAP",
               "sizeGib": "4"
             },
             {
               "type": "EXT4",
               "mountPoint": "/"
             }
           ],
           "raid": {
             "type": "RAID10",
             "disks": [
               {
                 "id": "1",
                 "type": "HDD",
                 "sizeGib": "1862"
               },
               {
                 "id": "2",
                 "type": "HDD",
                 "sizeGib": "1862"
               },
               {
                 "id": "3",
                 "type": "HDD",
                 "sizeGib": "1862"
               },
               {
                 "id": "4",
                 "type": "HDD",
                 "sizeGib": "1862"
               }
             ]
           }
         }
       ],
       "sshPublicKey": "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMYMj0PbB7ObhwL0********",
       "passwordLockboxSecret": {
         "secretId": "e6q44i0gmlrh********",
         "versionId": "e6q3ba84ur0a********",
         "key": "password"
       }
     },
     "labels": {
       "key": "bms"
     }
   }' \
   "POST https://baremetal.api.cloud.yandex.net/baremetal/v1alpha/servers/<server_ID>"
  ```

  Where:
  * `folderId`: ID of the [folder](../../../resource-manager/concepts/resources-hierarchy.md#folder) where you want to create your server.
  * `name`: Server name. The name must be unique within the folder.

    * 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.

  * `description`: Server description. This is an optional parameter.
  * `labels`: Resource labels in `key:value` format. This is an optional parameter.
  * `hardwarePoolId`: ID of the [pool](../../concepts/servers.md#server-pools) to lease a server from.
  * `configurationId`: [Server configuration](../../concepts/server-configurations.md) ID.
  * `rentalPeriodId`: Server lease period. The possible values are `1-day`, `1-month`, `3-months`, `6-months` or `1-year`.
  * `networkInterfaces[]`: Network interfaces:
    * `id`: Network interface ID. It is not specified when creating a server.
    * `privateSubnetId`: [Private subnet](../../concepts/private-network.md#private-subnet) ID.
    * `publicSubnetId`: [Dedicated public subnet](../../concepts/public-network.md#public-subnet) ID. This is an optional parameter.

      {% note warning %}

      The dedicated public subnet [does not have](../../concepts/dhcp.md#dhcp-public-subnet) a DHCP server; therefore, on the network interface of the server connected to such subnet, you should manually configure a static IP address from the subnet’s range of available public IP addresses and specify the default gateway address.

      {% endnote %}

  * `osSettingsSpec`: OS settings. To lease a server without an operating system, skip this parameter.
  Possible settings:
    * `imageId`: ID of an available Yandex Cloud Marketplace public OS [image](../../concepts/images.md#marketplace-images).
    * `storages[]`: Disk partitioning settings. This is an optional parameter. Possible settings:
      * `partitions[]`: Disk partition:
        * `type`: File system. The possible values are `EXT4`, `EXT3`, `SWAP`, or `XFS`.
        * `sizeGib`: Partition size in GB.
        * `mountPoint`: Mount point.
      * `disk`: Disk settings:
        * `id`: Disk ID.
        * `type`: Disk type. The possible values are `HDD`, `SSD`, and `NVME`.
        * `sizeGib`: Disk size in GB.
      * `raid`: RAID array settings:
        * `type`: RAID type. The possible values are `RAID0`, `RAID1`, and `RAID10`.
        * `disks[]`: Disk array in a RAID configuration. Each disk contains the following fields: `id`, `type`, and `sizeGib`.
    * `sshPublicKey`: Public SSH key contents. You will need to [create](../../../compute/operations/vm-connect/ssh.md#creating-ssh-keys) your own SSH key pair to establish a secure server connection.
    * `userSshId`: SSH key user ID. This is an optional parameter.
    * `passwordPlainText`: Root user's password. This is an optional parameter.
  
      {% note warning %}
      
      This option requires you to maintain password security. Save the password you generated in a secure location. Yandex Cloud does not store it, and you will not be able to retrieve it once the server is deployed.
      
      {% endnote %}
  
    * `passwordLockboxSecret`: Yandex Lockbox [secret](../../../lockbox/concepts/secret.md):
      * `secretId`: Secret ID.
      * `versionId`: Secret version.
      * `key`: Secret key.

  Result:

  ```bash
  {
    "id": "e0q5abc123def4********",
    "description": "Server create",
    "createdAt": "2025-12-14T18:03:38.240Z",
    "createdBy": "ajeb9l33h6mu********",
    "modifiedAt": "2025-12-14T18:03:38.240Z",
    "done": true,
    "metadata": {
      "serverId": "ly56xpblirh4********"
    },
    "response": {
      "id": "ly56xpblirh4********",
      "cloudId": "b1g07hj5r6i4********",
      "folderId": "b1g07hj5r6i4********",
      "name": "bm-test-server",
      "description": "New Test Baremetal Server",
      "zoneId": "ru-central1",
      "hardwarePoolId": "ru-central1-m3",
      "status": "PROVISIONING",
      "osSettings": {
        "imageId": "ly5vyzcggvci********",
        "sshPublicKey": "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMYMj0PbB7ObhwL0z3********",
        "storages": [
          {
            "partitions": [
              {
                "type": "EXT3",
                "sizeGib": "9",
                "mountPoint": "/boot"
              },
              {
                "type": "SWAP",
                "sizeGib": "4"
              },
              {
                "type": "EXT4",
                "mountPoint": "/"
              }
            ],
            "raid": {
              "type": "RAID10",
              "disks": [
                {
                  "id": "1",
                  "type": "HDD",
                  "sizeGib": "1862"
                },
                {
                  "id": "2",
                  "type": "HDD",
                  "sizeGib": "1862"
                },
                {
                  "id": "3",
                  "type": "HDD",
                  "sizeGib": "1862"
                },
                {
                  "id": "4",
                  "type": "HDD",
                  "sizeGib": "1862"
                }
              ]
            }
          }
        ]
      },
      "networkInterfaces": [
        {
          "id": "e0q5abc123def4********",
          "macAddress": "00:1a:4b:23:*:*",
          "ipAddress": "192.168.*.*",
          "privateSubnet": {
            "privateSubnetId": "ly52xefxa2hi********"
          }
        },
        {
          "id": "e0q5abc123def4********",
          "macAddress": "00:1a:4b:23:*:*",
          "ipAddress": "93.158.*.*",
          "publicSubnet": {
            "publicSubnetId": "ly52yjugkj57********"
          }
        }
      ],
      "configurationId": "ly5fcdnlzp7j********",
      "disks": [
        {
          "id": "1",
          "type": "HDD",
          "sizeGib": "1862"
        },
        {
          "id": "2",
          "type": "HDD",
          "sizeGib": "1862"
        },
        {
          "id": "3",
          "type": "HDD",
          "sizeGib": "1862"
        },
        {
          "id": "4",
          "type": "HDD",
          "sizeGib": "1862"
        }
      ],
      "createdAt": "2025-12-14T18:03:38.240Z",
      "labels": {
        "key": "bms"
      }
    }
  }
  ```

  Follow the status of the operation by the `done` field.

{% endlist %}

#### See also {#see-also}

* [Renting a custom-configured server](custom-server-lease.md)