Creating a VM from disks
You can create a VM from existing disks. Make sure the disks reside in one of the availability zones and are not added to other VMs.
When selecting a disk to attach to your VM, you can specify whether to delete that disk when deleting the VM. You can enable this option when creating or updating a VM, or when attaching a new disk to it.
-
In the management console
, select the folder where you want to create your VM. -
In the list of services, select Compute Cloud.
-
In the left-hand panel, select
Virtual machines. -
Click Create virtual machine.
-
Under Boot disk image, select an image.
-
Under Location, select an availability zone for your VM.
-
Add a disk:
- Under Disks and file storages, click Add.
- In the window that opens, select Disk →
Connect existing disk
. - Select the disk you need.
- Optionally, enable Additional in the Delete along with the virtual machine field if you need this disk automatically deleted when deleting the VM.
- Click Add disk.
-
Optionally, to encrypt a boot disk or a secondary disk, under Disks and file storages, click
to the right of the disk name and configure encryption parameters for the disk:- Select Encrypted disk.
- In the KMS key field, select the key you want to use to encrypt the disk. To create a new key, click Create new key.
Warning
You can specify encryption settings only when creating a disk. You cannot disable or change disk encryption.
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.
Alert
If you destroy the key or its version used to encrypt a disk, image, or snapshot, access to the data will be irrevocably lost. For details, see Destroying key versions.
-
Optionally, connect a file storage:
-
Under Disks and file storages, click Add.
-
In the window that opens, select File storage and choose the storage you want to connect from the list.
-
Click Add file storage.
-
-
-
Under Computing resources, select one of the preset configurations or create a custom one. To create a custom configuration:
- Go to the Custom tab.
- Select a platform.
- Specify the guaranteed performance and required number of vCPUs, as well as RAM size.
- Optionally, enable a software-accelerated network.
- Make your VM preemptible, if required.
-
Under Network settings:
-
In the Subnet field, enter the ID of a subnet in the new VM’s availability zone. Alternatively, you can select a cloud network from the list.
-
Each network must have at least one subnet. If your network has no subnets, create one by selecting Create subnet.
-
If there are no networks in the list, click Create network to create one:
- In the window that opens, specify the network name and select the folder where you want to create it.
- Optionally, select Create subnets to automatically create subnets in all availability zones.
- Click Create network.
-
-
In the Public IP address field, select a method for assigning an IP address:
Auto
: To assign a random IP address from the Yandex Cloud IP address pool. In this case, you can enable DDoS protection using the option below.List
: To select a public IP address from the list of previously reserved static addresses. For more information, see Converting a dynamic public IP address to static.No address
: Not to assign a public IP address.
-
Select the relevant security groups. If you leave this field empty, the default security group will be assigned to the VM.
-
Expand Additional and select a method for assigning internal addresses in the Internal IPv4 address field:
Auto
: To assign a random IP address from the pool of IP addresses available in the selected subnet.Manual
: To manually assign a private IP address to the VM.- Enable DDoS protection, if required. The option is available if you previously selected the automatic IP assignment method in the public address settings.
-
Optionally, create records for your VM in the DNS zone:
- Expand DNS settings for internal addresses and click Add record.
- Specify a zone, FQDN, and TTL for the record. When setting the FQDN, you can enable
Detect automatically
for the zone.
You can add multiple records to internal DNS zones. For more information, see Cloud DNS integration with Compute Cloud. - To create another record, click Add record.
If you want to add another network interface to your VM, click Add network interface and repeat the settings from this step for the new interface. You can add up to eight network interfaces to a single VM.
-
-
Under Access:
-
Select Access by OS Login to connect and manage access to the new VM using OS Login in Yandex Cloud Organization.
With OS Login, you can connect to VMs using SSH keys and SSH certificates via a standard SSH client or the Yandex Cloud CLI. OS Login enables rotating the SSH keys used to access VMs, providing the most secure access option.
-
If you prefer not to use OS Login, select SSH key and specify the following VM access data:
-
Under Login, enter a username.
Alert
Do not use
root
or other usernames reserved by the OS. To perform operations requiring superuser privileges, use thesudo
command. -
In the SSH key field, select the SSH key saved in your organization user profile.
If there are no saved SSH keys in your profile, or you want to add a new key:
- Click Add key.
- Enter a name for the SSH key.
- Upload or paste the contents of the public key file. You need to create a key pair for the SSH connection to a VM yourself.
- Click Add.
The SSH key will be added to your organization user profile.
If users cannot add SSH keys to their profiles in the organization, the added public SSH key will only be saved to the user profile of the VM being created.
-
If you want to add multiple users with SSH keys to the VM at the same time, specify these users' data under Metadata. You can also use metadata to install additional software on a VM when creating it.
In public Linux images provided by Yandex Cloud, the functionality of connecting over SSH using login and password is disabled by default.
-
-
Under General information, enter a name for the VM:
- It must be 2 to 63 characters long.
- It may contain lowercase Latin letters, numbers, and hyphens.
- It must start with a letter and cannot end with a hyphen.
Note
The VM name is used to generate an internal FQDN, which is set only once, when you create the VM. If the internal FQDN is important to you, make sure to choose an appropriate name for your VM.
-
Under Additional:
-
Optionally, select or create a service account. With a service account, you can flexibly configure access permissions for your resources.
-
Optionally, enable access to the serial console.
-
Optionally, under Backup, enable Connect and select or create a backup policy to make automatic backups of your VMs using Cloud Backup.
For more information, see Connecting Compute Cloud VMs and Yandex BareMetal servers to Cloud Backup.
-
Optionally, under Monitoring, enable Agent for delivering metrics to configure delivering metrics to Yandex Monitoring.
-
Optionally, under Placement, select a VM placement group.
-
-
Click Create VM.
If you do not have the Yandex Cloud CLI yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder through the --folder-name
or --folder-id
parameter.
-
See the description of the CLI command for creating a VM:
yc compute instance create --help
-
Get a list of disks in the default folder:
yc compute disk list
Result:
+----------------------+--------------+-------------+-------------------+--------+----------------------+-----------------+-------------+ | ID | NAME | SIZE | ZONE | STATUS | INSTANCE IDS | PLACEMENT GROUP | DESCRIPTION | +----------------------+--------------+-------------+-------------------+--------+----------------------+-----------------+-------------+ | a7lqgbt0bb9s******** | first-disk | 20401094656 | ru-central1-a | READY | a7lcvu28njbh******** | | | | a7lv5j5hm1p1******** | second-disk | 21474836480 | ru-central1-a | READY | | | | +----------------------+--------------+-------------+-------------------+--------+----------------------+-----------------+-------------+
-
Select the IDs (
ID
) or names (NAME
) of the disks you need. -
Create a VM in the default folder:
yc compute instance create \ --name first-instance \ --zone ru-central1-a \ --network-interface subnet-name=default-a,nat-ip-version=ipv4 \ --use-boot-disk disk-name=first-disk \ --attach-disk disk-name=second-disk \ --ssh-key ~/.ssh/id_ed25519.pub
This command will create a VM with the following parameters:
-
Name:
first-instance
Note
The VM name is used to generate an internal FQDN, which is set only once, when you create the VM. If the internal FQDN is important to you, make sure to choose an appropriate name for your VM.
-
Availability zone:
ru-central1-a
-
Subnet:
default-a
-
With a public IP address and two disks
To specify whether to delete the disk when deleting the VM, set the
--auto-delete
flag:yc compute instance create \ --name first-instance \ --zone ru-central1-a \ --network-interface subnet-name=default-a,nat-ip-version=ipv4 \ --use-boot-disk disk-name=first-disk,auto-delete=yes \ --attach-disk disk-name=second-disk,auto-delete=yes \ --ssh-key ~/.ssh/id_ed25519.pub
If you want to add multiple network interfaces to your VM, specify the
--network-interface
parameter as many times as you need. You can add up to eight network interfaces to a single VM. -
If you don't have Terraform, install it and configure the Yandex Cloud provider.
To create a VM from disks:
-
In the configuration file, define the parameters of the resources you want to create:
resource "yandex_compute_disk" "boot-disk" { name = "<disk_name>" type = "<disk_type>" zone = "<availability_zone>" size = "<disk_size>" image_id = "<image_ID>" } resource "yandex_compute_instance" "vm-1" { name = "vm-from-disks" allow_stopping_for_update = true platform_id = "standard-v3" zone = "<availability_zone>" resources { cores = <number_of_vCPU_cores> memory = <RAM_in_GB> } boot_disk { disk_id = <boot_disk_ID> } secondary_disk { disk_id = "<secondary_disk_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>" network_id = "${yandex_vpc_network.network-1.id}" }
Where:
-
yandex_compute_disk
: Boot disk description:-
name
: Disk name. -
type
: Disk type. -
zone
: Availability zone the disk will be in. -
size
: Disk size in GB. -
image_id
: ID of the image to create the VM from. You can get the image ID from the list of public images.You can also view image IDs in the management console
when creating a VM or in Cloud Marketplace on the image page under Product IDs.
-
-
yandex_compute_instance
: VM description:-
name
: VM name. -
allow_stopping_for_update
: Permission to stop the VM for updates. Set totrue
if you plan to change your VM's network settings or computing resources using Terraform. The default value isfalse
. -
platform_id
: Platform. -
zone
: Availability zone the VM will be in. -
resources
: Number of vCPUs and amount of RAM available to the VM. The values must match the selected platform. -
boot_disk
: Boot disk settings. Specify the disk ID. -
secondary_disk
: Secondary disk to connect to the VM. Specify the ID of the secondary disk. If there is no disk, create one. -
network_interface
: VM network interface settings. Specify the ID of the selected subnet. To automatically assign a public IP address to the VM, setnat = true
.If you want to add multiple network interfaces to your VM, specify the
network_interface
section as many times as you need. You can add up to eight network interfaces to a single VM. -
metadata
: In metadata, provide the public key for SSH access to the VM. For more information, see VM metadata.
-
-
yandex_vpc_network
: Cloud network description. -
yandex_vpc_subnet
: Description of the subnet to connect your VM to.
Note
If you already have suitable resources, such as a cloud network and subnet, you do not need to redefine them. Specify their names and IDs in the appropriate parameters.
For more information about the resources you can create with Terraform, see the relevant provider documentation
. -
-
Create the resources:
-
In the terminal, change to the folder where you edited the configuration file.
-
Make sure the configuration file is correct using the command:
terraform validate
If the configuration is correct, the following message is returned:
Success! The configuration is valid.
-
Run the command:
terraform plan
The terminal will display a list of resources with parameters. No changes are made at this step. If the configuration contains errors, Terraform will point them out.
-
Apply the configuration changes:
terraform apply
-
Confirm the changes: type
yes
in the terminal and press Enter.
All the resources you need will then be created in the specified folder. You can check the new resources and their settings using the management console
. -
Use the create REST API method for the Instance resource or the InstanceService/Create gRPC API call.