Yandex Cloud
  • Services
  • Solutions
  • Why Yandex Cloud
  • Blog
  • Pricing
  • Documentation
  • Contact us
Get started
Language / Region
Yandex project
© 2023 Yandex.Cloud LLC
Yandex Compute Cloud
  • Getting started
    • Overview
    • Creating a Linux VM
    • Creating instance groups
  • Step-by-step instructions
    • All instructions
    • Creating VMs
      • Creating a Linux VM
      • Creating a VM from a set of disks
      • Creating a VM with disks from snapshots
      • Creating a VM from a custom image
      • Creating a VM with a GPU
      • Making a VM preemptible
    • DSVM
      • Overview
      • Creating a VM from a public DSVM image
    • Placement groups
      • Creating a placement group
      • Deleting a placement group
      • Creating a VM in a placement group
      • Adding a VM to a placement group
      • Removing a VM from a placement group
    • Images with pre-installed software
      • Creating a VM from a public image
      • Configuring software
      • Running a VM based on a public image
      • Getting a list of public images
    • Getting information about a VM
      • Getting information about a VM
      • Getting serial port's output
    • Managing VMs
      • Stopping and starting a VM
      • Attaching a disk to a VM
      • Detaching a disk from a VM
      • Moving a VM to a different availability zone
      • Moving a VM to another folder
      • Attaching a public IP address to a VM
      • Detaching a public IP address from a VM
      • Making a VM's public IP address static
      • Updating a VM
      • Changing VM computing resources
      • Deleting a VM
    • Working on VMs
      • Connecting to a VM via SSH
      • Connecting to a VM via RDP
      • Connecting to a VM via PowerShell
      • Working with Yandex Cloud from inside a VM
      • Installing NVIDIA drivers
      • Restoring access to a VM
    • Managing the password reset agent
      • Installing the agent
    • Creating a disk
      • Creating an empty disk
      • Creating an empty disk with a large block
      • Creating a non-replicated disk
    • Disk management
      • Updating a disk
      • Configuring disk snapshot schedules
      • Moving a disk to another folder
      • Deleting a disk
    • Disk snapshots
      • Creating snapshots
      • Deleting snapshots
      • Creating a snapshot schedule
      • Changing a snapshot schedule
      • Interrupting and starting a snapshot schedule
      • Deleting a snapshot schedule
    • Disk placement groups
      • Creating a disk placement group
      • Removing a disk from a placement group
    • Creating an image
      • Preparing a disk image
      • Uploading your image
      • Creating an image from a disk
      • Creating an image from a disk snapshot
      • Creating an image from other custom image
    • Managing images
      • Getting a list of images
      • Deleting a disk image
    • File storage
      • Creating file storage
      • Attaching file storage to a VM
      • Detaching file storage from a VM
      • Updating file storage
      • Deleting file storage
    • Managing the serial console
      • Getting started
      • Connecting to a serial console via SSH
      • Connecting to a serial console via the CLI
      • Starting your terminal in the Windows serial console (SAC)
      • Disabling access to the serial console
    • Creating instance groups
      • Creating a fixed-size instance group
      • Creating a fixed-size instance group with a network load balancer
      • Creating a fixed-size instance group with an L7 load balancer
      • Creating an automatically scaled instance group
      • Creating an instance group from a Container Optimized Image
      • Creating an instance group based on the YAML specification
    • Getting information about instance groups
      • Getting a list of instance groups
      • Getting information about an instance group
      • Getting a list of instances in a group
    • Managing instance groups
      • Editing an instance group
      • Edit an instance group based on the YAML specification
      • Configuring application health check on the VM
      • Updating a group
        • Incremental update
        • Uninterrupted updates
      • Pausing an instance group
      • Resuming an instance group
      • Stopping an instance group
      • Starting an instance group
      • Deleting an instance group
    • Dedicated hosts
      • Creating a group of dedicated hosts
      • Creating a VM in a group of dedicated hosts
      • Creating a VM on a dedicated host
  • Yandex Container Solution
  • Practical guidelines
    • All tutorials
    • Configuring clock synchronization using NTP
    • Running instance groups with auto scaling
    • Automatically scaling an instance group for handling messages from a queue
    • Updating an instance group under load
    • Transferring logs from a VM instance to Yandex Cloud Logging
    • Building a VM image with a set of infrastructure tools using Packer
    • Creating a VM backup with Hystax Acura Backup
  • Concepts
    • Relationship between resources
    • Virtual machines
      • Overview
      • Platforms
      • vCPU performance levels
      • Preemptible VMs
      • Network on a VM
      • Software-accelerated network
      • Live migration
      • Placement groups
      • Statuses
      • Metadata
    • Graphics accelerators
    • Disks and file storage
      • Overview
      • Disks
      • Disk snapshots
      • Creating scheduled snapshots
      • Non-replicated disk placement groups
      • File storage
      • Read and write operations
    • Images
    • Instance groups
      • Overview
      • Access
      • YAML specification
      • Instance template
      • Variables in an instance template
      • Policies
        • Overview
        • Allocation policy
        • Deployment policy
        • Scaling policy
      • Scaling types
      • Auto-healing
      • Updating
        • Overview
        • Allocating instances across zones
        • Deployment algorithm
        • Rules for updating virtual machines
        • Changing secondary disks in an instance template
      • Stopping and pausing an instance group
      • Statuses
    • Dedicated hosts
    • Backups
    • Quotas and limits
  • Access management
  • Pricing policy
    • Current pricing policy
    • Archive
      • Before January 1, 2019
      • From January 1 to March 1, 2019
      • From March 1 to May 1, 2019
  • API reference
    • Authentication in the API
    • gRPC
      • Overview
      • DiskPlacementGroupService
      • DiskService
      • DiskTypeService
      • FilesystemService
      • HostGroupService
      • HostTypeService
      • ImageService
      • InstanceService
      • PlacementGroupService
      • SnapshotScheduleService
      • SnapshotService
      • ZoneService
      • InstanceGroupService
      • OperationService
    • REST
      • Overview
      • DiskPlacementGroup
        • Overview
        • create
        • delete
        • get
        • list
        • listDisks
        • listOperations
        • update
      • Disk
        • Overview
        • create
        • delete
        • get
        • list
        • listOperations
        • move
        • update
      • DiskType
        • Overview
        • get
        • list
      • Filesystem
        • Overview
        • create
        • delete
        • get
        • list
        • listOperations
        • update
      • HostGroup
        • Overview
        • create
        • delete
        • get
        • list
        • listHosts
        • listInstances
        • listOperations
        • update
      • HostType
        • Overview
        • get
        • list
      • Image
        • Overview
        • create
        • delete
        • get
        • getLatestByFamily
        • list
        • listOperations
        • update
      • Instance
        • Overview
        • addOneToOneNat
        • attachDisk
        • attachFilesystem
        • create
        • delete
        • detachDisk
        • detachFilesystem
        • get
        • getSerialPortOutput
        • list
        • listOperations
        • move
        • removeOneToOneNat
        • restart
        • start
        • stop
        • update
        • updateMetadata
        • updateNetworkInterface
      • PlacementGroup
        • Overview
        • create
        • delete
        • get
        • list
        • listInstances
        • listOperations
        • update
      • SnapshotSchedule
        • Overview
        • create
        • delete
        • disable
        • enable
        • get
        • list
        • listDisks
        • listOperations
        • listSnapshots
        • update
        • updateDisks
      • Snapshot
        • Overview
        • create
        • delete
        • get
        • list
        • listOperations
        • update
      • Zone
        • Overview
        • get
        • list
      • Operation
        • Overview
        • get
      • InstanceGroup
        • Overview
        • list
        • get
        • listLogRecords
        • updateFromYaml
        • updateAccessBindings
        • pauseProcesses
        • stop
        • start
        • delete
        • listInstances
        • createFromYaml
        • update
        • setAccessBindings
        • listOperations
        • create
        • listAccessBindings
        • resumeProcesses
  • Questions and answers
    • General questions
    • Virtual machines
    • Connection
    • Disks, snapshots, and images
    • Disaster recovery
    • Instance groups
    • Monitoring
    • Licensing
    • All questions on one page
  1. Step-by-step instructions
  2. Creating VMs
  3. Creating a Linux VM

Creating a VM from a public Linux image

Written by
Yandex Cloud
,
improved by
    Management console
    CLI
    API
    Terraform

    To create a VM:

    1. In the management console, select the folder to create the virtual machine in.

    2. In the list of services, select Compute Cloud.

    3. Click Create VM.

    4. Under Basic parameters:

      • Enter a name and description for the VM. Naming requirements:

        • The length can be from 3 to 63 characters.
        • It may contain lowercase Latin letters, numbers, and hyphens.
        • The first character must be a letter. The last character can't be a hyphen.

        Note

        The VM name is used to generate an internal FQDN only once: when creating a VM. If the internal FQDN is important to you, choose an appropriate name for the VM at the creation stage.

      • Select an availability zone to put your virtual machine in.

    5. Under Image/boot disk selection, select an image and a Linux-based OS version.

    6. (optional) Under Disk and file storage, click the Disks tab and configure a boot disk:

      • Select the disk type.

      • Specify the necessary disk size.

        If you wish to create a virtual machine from an existing disk, under Disks and file storage, add a disk:

        • Click Add disk.
        • Enter the disk name.
        • Select the disk type.
        • Specify the desired block size.
        • Specify the necessary disk size.
        • (optional) Enable the Delete with the VM option if you need to automatically delete the disk when deleting the VM it will be attached to.
        • Select Disk as content.
        • Click Add.
    7. (optional) Under Disks and file storage, click the File storage tab and connect a file store:

      • Click Connect file storage.
      • In the resulting window, select a file store.
      • Enter a device name.
      • Click Connect file storage.
    8. Under Computing resources:

      • Choose a platform.
      • Specify the guaranteed share and the required number of vCPUs, as well as the amount of RAM.
      • If necessary, make your VM preemptible.
      • (optional) Enable a software-accelerated network.
    9. Under Network settings:

      • Enter a subnet ID or select a cloud network from the list.
        If you don't have a network, click Create network to create one:

        • In the window that opens, enter the network name and folder to host the network.
        • (optional) To automatically create subnets, select the Create subnets option.
        • Click Create.
          Each network must have at least one subnet. If there is no subnet, create one by selecting Add subnet.
      • In the Public IP field, choose a method for assigning an IP address:

        • Auto: Assign a random IP address from the Yandex Cloud IP pool. With this, you can enable DDoS protection using the option below.
        • List: Select a public IP address from the list of previously reserved static addresses. For more information, see Making a dynamic public IP address static.
        • No address: Don't assign a public IP address.
      • In the Internal address field, select the method for assigning internal addresses: Auto or Manual.

      • (optional) Create records for the VM in the DNS zone:

        • Expand DNS settings for internal addresses and click Add record.
        • Specify the zone, FQDN, and TTL for the record. When setting the FQDN, you can select Detect automatically for the zone.
          You can add multiple records to internal DNS zones. For more information, see Cloud DNS integration with Compute Cloud.
      • Select appropriate security groups (if there is no corresponding field, the virtual machine will be enabled for all incoming and outgoing traffic).

    10. (optional) To automatically back up your instances using Cloud Backup, under Backup, select the option of connecting an instance to the service.

      The option shows up if you requested access to the service from our technical support and selected a supported operating system for your VM. For more information about setting up a VM, see Connecting Compute Cloud instances to Cloud Backup.

    11. Under Access, specify the data required to access the VM:

      • (optional) Select or create a service account. By using a service account, you can flexibly configure access rights for your resources.

      • Enter the username in the Login field.

        Alert

        Don't use the username root or other names reserved by the operating system. To perform operations that require superuser permissions, use the command sudo.

      • In the SSH key field, paste the contents of the public key file. You need to create a key pair for SSH connection yourself.

      • If required, grant access to the serial console.

    12. (optional) Under Placement, select a VM placement group.

    13. Click Create VM.

    The virtual machine appears in the list. When a VM is created, it is assigned an IP address and hostname (FQDN).

    If you don't have the Yandex Cloud command line interface yet, install and initialize it.

    The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

    1. View the description of the CLI command for creating a VM:

      yc compute instance create --help
      
    2. Prepare the key pair (public and private keys) for SSH access to the VM.

    3. Select a public image Cloud Marketplace based on a Linux OS (for example, CentOS 7).

      To get a list of available images, run the following command:

      yc compute image list --folder-id standard-images
      

      Result:

      +----------------------+-------------------------------------+--------------------------+----------------------+--------+
      |          ID          |                NAME                 |          FAMILY          |     PRODUCT IDS      | STATUS |
      +----------------------+-------------------------------------+--------------------------+----------------------+--------+
      ...
      | fdvk34al8k5nltb58shr | centos-7-1549279494                 | centos-7                 | dqni65lfhvv2den5gtv9 | READY  |
      | fdv7ooobjfl3ts9gqp0q | windows-2016-gvlk-1548913814        | windows-2016-gvlk        | dqnnc72gj2ist3ktjj1p | READY  |
      | fdv4f5kv5cvf3ohu4flt | ubuntu-1604-lts-1549457823          | ubuntu-1604-lts          | dqnnb6dc7640c5i968ro | READY  |
      ...
      +----------------------+-------------------------------------+--------------------------+----------------------+--------+
      
    4. Select a subnet:

      yc vpc subnet list
      

      Result:

      +----------------------+-----------------------+----------------------+----------------+---------------+-----------------+
      |          ID          |         NAME          |      NETWORK ID      | ROUTE TABLE ID |     ZONE      |      RANGE      |
      +----------------------+-----------------------+----------------------+----------------+---------------+-----------------+
      | b0c6n43f9lgh3695v2k2 | default-ru-central1-c | enpe3m3fa00udao8g5lg |                | ru-central1-c | [10.130.0.0/24] |
      | e2l2da8a20b33g7o73bv | default-ru-central1-b | enpe3m3fa00udao8g5lg |                | ru-central1-b | [10.129.0.0/24] |
      | e9bnlm18l70ao30pvfaa | default-ru-central1-a | enpe3m3fa00udao8g5lg |                | ru-central1-a | [10.128.0.0/24] |
      +----------------------+-----------------------+----------------------+----------------+---------------+-----------------+
      
    5. Create a VM in the default folder:

      yc compute instance create \
        --name first-instance \
        --zone ru-central1-a \
        --network-interface subnet-name=default-ru-central1-a,nat-ip-version=ipv4 \
        --create-boot-disk image-folder-id=standard-images,image-family=centos-7 \
        --ssh-key ~/.ssh/id_ed25519.pub
      

      Where:

      • name: VM name.

        Note

        The VM name is used to generate an internal FQDN only once: when creating a VM. If the internal FQDN is important to you, choose an appropriate name for the VM at the creation stage.

      • zone: Availability zone that corresponds to the selected subnet.

      • subnet-name: Name of the selected subnet.

      • image-family: An image family, such as centos-7. This option lets you install the latest version of the operating system from the specified family.

      • nat-ip-version=ipv4: Public IP. To create a VM without a public IP, disable the parameter.

      • ssh-key: Path to the public SSH key. The user yc-user will be automatically created on the VM for this key.

    When a VM is created, it is assigned an IP address and hostname (FQDN). This data can be used for SSH access.

    You can make a public IP address static. For more information, see Making a VM's public IP address static.

    Create a VM using the Create method for the Instance resource:

    1. Prepare the key pair (public and private keys) for SSH access to the VM.

    2. Get an IAM token for authentication in these examples:

      • Instructions for users with a Yandex account.
      • Instructions for a service account.
      • Instructions for a federated account.
    3. Get the ID of the folder.

    4. Get information about the image to create your virtual machine from (image ID and minimum disk size):

      • If you know the image family, get information about the latest image in this family:
        export IAM_TOKEN=CggaATEVAgA...
        export FAMILY=ubuntu-1804
        curl -H "Authorization: Bearer ${IAM_TOKEN}" \
          "https://compute.api.cloud.yandex.net/compute/v1/images:latestByFamily?folderId=standard-images&family=${FAMILY}"
        
      • To learn more about the image, see the list of public images.
    5. Get the subnet ID and availability zone ID. Specify the ID of the folder where the subnet was created in your request:

      export IAM_TOKEN=CggaATEVAgA...
      export FOLDER_ID=b1gvmob95yysaplct532
      curl -H "Authorization: Bearer ${IAM_TOKEN}" \
        "https://vpc.api.cloud.yandex.net/vpc/v1/subnets?folderId=${FOLDER_ID}"
      {
       "subnets": [
        {
         "v4CidrBlocks": [
          "10.130.0.0/24"
         ],
         "id": "b0c6n43ftldh30l0vfg2",
         "folderId": "b1gvmob95yysaplct532",
         "createdAt": "2018-09-23T12:15:00Z",
         "name": "default-ru-central1-a",
         "description": "Auto-created default subnet for zone ru-central1-a",
         "networkId": "enpe3m3fagludao8aslg",
         "zoneId": "ru-central1-a"
        },
        ...
       ]
      }
      
    6. Create a file where the body contains your request for VM creation (for example, body.json):

      {
        "folderId": "b1gvmob95yysaplct532",
        "name": "instance-demo-no-pwauth",
        "zoneId": "ru-central1-a",
        "platformId": "standard-v3",
        "resourcesSpec": {
          "memory": "2147483648",
          "cores": "2",
        },
        "metadata": {
          "user-data": "#cloud-config\nusers:\n  - name: user\n    groups: sudo\n    shell: /bin/bash\n    sudo: ['ALL=(ALL) NOPASSWD:ALL']\n    ssh-authorized-keys:\n      - ssh-ed25519 AAAAB3N... user@example.com"
        },
        "bootDiskSpec": {
          "diskSpec": {
            "size": "2621440000",
            "imageId": "fd8rc75pn12fe3u2dnmb"
          }
        },
        "networkInterfaceSpecs": [
          {
            "subnetId": "b0c6n43ftldh30l0vfg2",
            "primaryV4AddressSpec": {
              "oneToOneNatSpec": {
                "ipVersion": "IPV4"
              }
            }
          }
        ]
      }
      

      Where:

      • folderId: ID of the folder.

      • name: Name to be assigned to the VM when it's created.

      • zoneId: Availability zone that corresponds to the selected subnet.

      • platformId: The platform.

      • resourceSpec: Resources available to the VM. The values must match the selected platform.

      • metadata: In the metadata, pass the public key for accessing the VM via SSH. For more information, see VM instance metadata.

      • bootDiskSpec: Boot disk settings. Specify the ID of the selected image and disk size. The disk size must not be below the minimum value specified in the image details.

      • networkInterfaceSpecs: Network setting.

      • subnetId: ID of the selected subnet.

      • primaryV4AddressSpec: IP address to be assigned to the VM. To add a public IP to your VM, please specify:

        ```
        "primaryV4AddressSpec": {
            "oneToOneNatSpec": {
              "ipVersion": "IPV4"
            }
          }
        ```
        

      Read more about the request body format in the API reference.

    7. Create a virtual machine:

      export IAM_TOKEN=CggaATEVAgA...
      curl -X POST \
        -H "Content-Type: application/json" \
        -H "Authorization: Bearer ${IAM_TOKEN}" \
        -d '@body.json' \
        https://compute.api.cloud.yandex.net/compute/v1/instances
      

    When a VM is created, it is assigned an IP address and hostname (FQDN). This data can be used for SSH access.

    You can make a public IP address static. For more information, see Making a VM's public IP address static.

    If you don't have Terraform, install it and configure the Yandex Cloud provider.

    1. In the configuration file, describe the parameters of resources that you want to create:

      resource "yandex_compute_instance" "vm-1" {
      
        name        = "linux-vm"
        platform_id = "standard-v3"
        zone        = "<availability zone>"
      
        resources {
          cores  = "<number of vCPU cores>"
          memory = "<RAM amount, GB>"
        }
      
        boot_disk {
          initialize_params {
            image_id = "<image ID>"
          }
        }
      
        network_interface {
          subnet_id = "${yandex_vpc_subnet.subnet-1.id}"
          nat       = true
        }
      
        metadata = {
          ssh-keys = "<username>:<SSH key contents>"
        }
      }
      
      resource "yandex_vpc_network" "network-1" {
        name = "network1"
      }
      
      resource "yandex_vpc_subnet" "subnet-1" {
        name           = "subnet1"
        zone           = "<availability zone>"
        v4_cidr_blocks = ["192.168.10.0/24"]
        network_id     = "${yandex_vpc_network.network-1.id}"
      }
      

      Where:

      • yandex_compute_instance: Description of the VM:
        • name: VM name.
        • platform_id: The platform.
        • zone: ID of the availability zone that will host your VM.
        • resources: The number of vCPU cores and the amount of RAM available to the VM. The values must match the selected platform.
        • boot_disk: Boot disk settings. Specify the ID of the selected image. You can get the image ID from the list of public images.
        • network_interface: Network settings. Specify the ID of the selected subnet. To automatically assign a public IP address to the VM, set nat = true.
        • metadata: In the metadata, pass the public key for accessing the VM via SSH. For more information, see VM instance metadata.
      • yandex_vpc_network: Description of the cloud network.
      • yandex_vpc_subnet: Description of subnet your virtual machine will connect to.

      Note

      If you already have suitable resources, such as a cloud network and subnet, you don't need to describe them again. Use their names and IDs in the appropriate parameters.

      For more information on resources that you can create with Terraform, see the provider documentation.

    2. Make sure that the configuration files are correct.

      1. In the command line, go to the directory where you created the configuration file.

      2. Run the check using the command:

        terraform plan
        

      If the configuration is described correctly, the terminal displays a list of created resources and their parameters. If the configuration contains errors, Terraform will point them out.

    3. Deploy the cloud resources.

      1. If the configuration doesn't contain any errors, run the command:

        terraform apply
        
      2. Confirm that you want to create the resources.

      Afterwards, all the necessary resources are created in the specified folder. You can check that the resources are there with the correct settings using the management console.

    When a VM is created, it is assigned an IP address and hostname (FQDN). This data can be used for SSH access.

    You can make a public IP address static. For more information, see Making a VM's public IP address static.

    See also

    • Connecting to a Linux VM via SSH

    Was the article helpful?

    Language / Region
    Yandex project
    © 2023 Yandex.Cloud LLC