Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • 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
© 2026 Direct Cursus Technology L.L.C.
Yandex BareMetal
  • Getting started
    • All guides
      • Leasing a server
      • Getting information about a server
      • Updating a server
      • Connecting to the KVM console
      • Stopping and starting a server
      • Cancel a server lease
      • Uploading a custom OS image
      • Connecting an existing BareMetal server to Cloud Backup
      • Using the Rescue CD
      • Configuring the MC-LAG aggregation group
      • Resetting a password on the server
      • Replacing a disk in a RAID array
      • Adding a new SSH key for a user
      • Restoring the OS bootloader
      • Disk status analysis with HW Watcher
    • Overview
      • Overview
      • Server configurations
      • Disk status analysis
      • Additional server settings
      • Overview
      • DHCP
      • MC-LAG
      • Restrictions in BareMetal networks
    • Images
    • Quotas and limits
    • All tutorials
    • Connecting an existing BareMetal server to Cloud Backup
    • Configuring VRRP for a cluster of BareMetal servers
    • Establishing network connectivity in a BareMetal private subnet
    • Establishing network connectivity between BareMetal and Virtual Private Cloud private subnets
    • Establishing network connectivity between a BareMetal private subnet and on-premise resources
    • Delivering USB devices to a BareMetal server or virtual machine
    • Configuring an OPNsense firewall in high availability cluster mode
    • Deploying a web app on BareMetal servers with an L7 load balancer and Smart Web Security protection
    • Connecting a BareMetal server as an external node to a Managed Service for Kubernetes cluster
  • Monitoring metrics
  • Audit Trails events
  • Access management
  • Pricing policy
  • FAQ
  1. Step-by-step guides
  2. Servers
  3. Updating a server

Updating a server

Written by
Yandex Cloud
Improved by
Danila N.
Updated at December 17, 2025
Management console
CLI
  1. In the management console, select the folder the server belongs to.

  2. Go to BareMetal.

  3. Find the server you need in the list, click in its row, and select Edit.

  4. Push your changes to the server configuration:

    • Optionally, change the server's name in the Name field. Follow these naming requirements:

      • It must be from 2 to 63 characters long.
      • It can only contain lowercase Latin letters, numbers, and hyphens.
      • It must start with a letter and cannot end with a hyphen.
    • Optionally, add or update the server's description in the Description field.

    • Optionally, add or update the server's labels in the Labels field.

    • Optionally, update server lease duration under Lease conditions.

      Note

      The lease duration setting changes will apply only after the current server lease period expires.

    • Optionally, change the server's network settings in the Private subnet and Public address fields.

    • Optionally, in the Bandwidth field, change the server's bandwidth package. Available bandwidth packages:

      • 10 TB per day, connection capacity, 1 Gbit/s
      • 100 TB per day, connection capacity, 10 Gbit/s

      Note

      You can select a bandwidth package only for configurations with a public IP address and network cards of 10 Gbps or higher.

      After you increase bandwidth, it can be reduced only after 24 hours.

  5. Click Save changes.

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. View the description of the server update command:

    yc baremetal server update --help
    
  2. Update server:

    yc baremetal server update \
      --name <server_name> \
      --new-name <new_server_name> \
      --description <new_server_description> \
      --network-interfaces private-subnet-id=<new_private_subnet_ID> \
      --network-interfaces public-subnet-id=<new_public_subnet_ID> \
      --labels <label_key>=<label_value>
    

    Where:

    • --name: Server name.

    • --new-name: New server name. This is an optional setting.

    • --description: New server description. This is an optional setting.

    • --network-interfaces: New network settings. This is an optional setting. The possible values are:

      • private-subnet-id: ID of the new private subnet.
      • public-subnet-id: ID of the new dedicated public subnet.
    • --labels: New server labels. This is an optional setting.

ExampleExample

Update server name, description, and network settings:

CLI
  yc baremetal server update \
    --name demo-baremetal-server  \
    --new-name new-demo-baremetal-server  \
    --description "Updated BareMetal server" \
    --network-interfaces private-subnet-id=ly5rljahs3re4gw7bf6l \
    --network-interfaces public-subnet-id=ly5vr6tugxk75fynutzt

Result:

id: ly52dtzdi55r********
cloud_id: b1gia87mbaom********
folder_id: b1g0ijbfaqsn********
name: new-demo-baremetal-server
description: Updated 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

Was the article helpful?

Previous
Getting information about a server
Next
Connecting to the KVM console
© 2026 Direct Cursus Technology L.L.C.