Creating a VM from a public Linux image
-
In the management console
, select the folder to create your VM in. -
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 and a Linux-based OS version.
To create a VM instance from an existing boot disk, go to the Custom tab and select the boot disk you need. To update its settings, click
next to the disk name. -
Under Location, select an availability zone to place your VM in.
-
(Optional) Configure the boot disk in the Disks and file storages section:
-
Select the disk type.
-
Specify the required disk size.
-
(Optional) To encrypt a boot disk or a secondary disk, under Disks and file storages, click
to the right of the disk name and set encryption parameters for the disk:- Select Encrypted disk.
- In the KMS key field, select the key to encrypt the disk with. To create a new key, click Create new key.
- In the Service account field, select a service account with the
kms.keys.encrypterDecrypter
role for the specified key. To create a service account, click Create new account.
The encryption feature in Compute Cloud is currently at the Preview stage. To access it, open the resource creation page and click Request access under Encryption or contact support
.If you deactivate the key used to encrypt a disk 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 or snapshot, access to the data will be irrevocably lost. Learn more in Destroying key versions.
If you are creating a VM instance from an existing boot disk, update the settings of that disk in the Custom tab under Boot disk image at the top of the form.
-
-
(Optional) Add a secondary disk:
-
Under Disks and file storages, click Add
-
In the window that opens, select Disk. You can select an existing disk or create a new one, either empty or from a snapshot / image.
For example, to create a new empty disk:
- Select
Create new
. - In the Contents field, select
Empty
. - Specify the disk name.
- Select the disk type.
- Specify the required disk size and block size.
- (Optional) Enable the Additional option in the Delete along with the virtual machine field if you need to automatically delete this disk when deleting the VM.
- Click Add disk.
- Select
-
-
(Optional) Connect a file storage:
-
Under Disks and file storages, click Add.
-
In the window that opens, select File storage and select the storage you want to connect from the list.
If you do not have any file storages, click Create file storage to create a new one.
-
Click Add file storage.
-
-
-
Under Computing resources, select a preset configuration or create a new one. To create a configuration:
- Go to the Custom tab.
- Choose a platform.
- Specify the guaranteed share and required number of vCPUs, as well as RAM size.
- Enable a software-accelerated network if needed.
- If required, make your VM preemptible.
-
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 there is no subnet, create one by selecting Create subnet.
-
If you do not have a network, click Create network to create one:
- In the window that opens, enter the network name and select the folder to host the network.
- (Optional) Select the Create subnets option to automatically create subnets in all availability zones.
- Click Create network.
-
-
In the Public IP field, choose a method for assigning an IP address:
Auto
: 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
: 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
: Do not assign a public IP address.
-
Select the appropriate security groups. If you leave this field empty, the default security group will be assigned to the VM.
-
Expand the Additional section and select a method for internal IP address assignment in the Internal IPv4 address field:
Auto
: Assign a random IP address from the pool of IP addresses available in the selected subnet.List
: Select a private IP address from the list of previously reserved IP addresses. Click Reserve to reserve a private IP address in the selected subnet if needed.- Enable the DDoS protection option, if needed. The option is available if you previously selected the automatic IP assignment method in the public address settings.
-
(Optional) Create records for the VM in the DNS zone:
- Expand the DNS settings for internal addresses section 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. - To create another record, click Add record.
If you want to attach an additional 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, specify the data for access to the VM:
-
(Optional) Enable VM access via OS Login. The option is available for Linux images from Cloud Marketplace with
OS Login
in their names. -
Enter the username into the Login field.
Alert
Do not use
root
or other usernames reserved by the OS. To perform operations requiring superuser permissions, use thesudo
command. -
In the SSH key field, paste the contents of the public key file. You need to create a key pair for the SSH connection yourself. To learn how, see Connecting to a VM via SSH.
If you want to add several 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, specify the VM name:
- The name must be from 3 to 63 characters long.
- It may contain lowercase Latin letters, numbers, and hyphens.
- The first character must be a letter and the last character cannot 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.
-
Under Additional:
-
(Optional) Select or create a service account. With a service account, you can flexibly configure access rights for your resources.
-
(Optional) Grant access to the serial console.
-
(Optional) Under Backup, enable Connect and select or create a backup policy to back up your VMs automatically using Cloud Backup.
For more information, see Connecting Compute Cloud VMs to Cloud Backup.
-
(Optional) Under Monitoring, enable the Agent for delivering metrics option to configuire delivery of metrics to Yandex Monitoring.
-
(Optional) Under Placement, select a VM placement group.
-
-
Click Create VM.
The VM appears in the list. Once created, the VM is assigned an IP address and a host name (FQDN).
If you do not 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.
-
View the description of the CLI command to create a VM:
yc compute instance create --help
-
Prepare a key pair (public and private keys) for SSH access to the VM.
-
Select a Linux-based public image from Yandex Cloud Marketplace, e.g., CentOS 7.
To get a list of available images using the CLI, run this command:
yc compute image list --folder-id standard-images
Result:
+----------------------+-------------------------------------+--------------------------+----------------------+--------+ | ID | NAME | FAMILY | PRODUCT IDS | STATUS | +----------------------+-------------------------------------+--------------------------+----------------------+--------+ ... | fdvk34al8k5n******** | centos-7-1549279494 | centos-7 | dqni65lfhvv2******** | READY | | fdv7ooobjfl3******** | windows-2016-gvlk-1548913814 | windows-2016-gvlk | dqnnc72gj2is******** | READY | | fdv4f5kv5cvf******** | ubuntu-1604-lts-1549457823 | ubuntu-1604-lts | dqnnb6dc7640******** | READY | ... +----------------------+-------------------------------------+--------------------------+----------------------+--------+
-
Select a subnet:
yc vpc subnet list
Result:
+----------------------+---------------------------+----------------------+----------------+-------------------+-----------------+ | ID | NAME | NETWORK ID | ROUTE TABLE ID | ZONE | RANGE | +----------------------+---------------------------+----------------------+----------------+-------------------+-----------------+ | e9bnlm18l70a******** | default-ru-central1-a | enpe3m3fa00u******** | | ru-central1-a | [10.128.0.0/24] | +----------------------+---------------------------+----------------------+----------------+-------------------+-----------------+
-
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. The naming requirements are as follows:- The name must be from 3 to 63 characters long.
- It may contain lowercase Latin letters, numbers, and hyphens.
- The first character must be a letter and the last character cannot 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.
-
--zone
: Availability zone corresponding to the selected subnet. -
--network-interface
: VM network interface settings.subnet-name
: Name of the selected subnet.nat-ip-version=ipv4
: Public IP address. To create a VM without a public IP address, disable this parameter.
If you want to add multiple network interfaces to the VM, specify the
--network-interface
parameter as many times as you need. You can add up to eight network interfaces to a single VM. -
--create-boot-disk
: VM boot disk settings:image-family
: Image family, e.g.,centos-7
. This option allows you to install the latest version of the OS from the specified family.
-
--ssh-key
: Path to the file with the public SSH key. The VM will automatically create a user namedyc-user
for this key.When creating a VM from a Yandex Cloud Marketplace public image, make sure to provide an SSH key to the VM. By default, SSH access with a username and password is disabled for such images.
If you want to add several users with SSH keys to the VM at the same time, specify these users' data using the
--metadata-from-file
parameter. You can also use metadata to install additional software on a VM when creating it.
-
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.
-
In the configuration file, describe 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 = "linux-vm" allow_stopping_for_update = true platform_id = "standard-v3" zone = "<availability_zone>" resources { cores = "<number_of_vCPU_cores>" memory = "<RAM_GB>" } boot_disk { disk_id = yandex_compute_disk.boot-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>" v4_cidr_blocks = ["192.168.10.0/24"] 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 on the image page in Cloud Marketplace, under Product IDs.
-
-
yandex_compute_instance
: VM description.-
name
: VM name. -
allow_stopping_for_update
: Allow a VM instance to stop to make changes. Settrue
if you plan to change the network settings, computing resources, disks, or file storage for your VM using Terraform. The default value isfalse
. -
platform_id
: Platform. -
zone
: Availability zone the VM will be in. -
resources
: Number of vCPU cores and RAM available to the VM. The values must match the selected platform. -
boot_disk
: Boot disk settings. Specify the disk ID. -
network_interface
: VM's 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 the 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 the metadata, provide the public SSH key for accessing the VM. For more information, see VM metadata.If you want to add several users with SSH keys to the VM at the same time, specify the data of these users in a file and provide it under
metadata
. You can also use metadata to install additional software on a VM when creating it.
-
-
yandex_vpc_network
: Description of the cloud network. -
yandex_vpc_subnet
: Description of the subnet your VM will be connected to.
Note
If you already have suitable resources, such as a cloud network and subnet, you do not need to describe them again. Use their names and IDs in the appropriate parameters.
For more information about the resources you can create with Terraform, see the provider documentation
. -
-
Create 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 configuration 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.
Create a VM using the create REST API method for the Instance resource:
-
Prepare a key pair (public and private keys) for SSH access to the VM.
-
Get an Yandex Identity and Access Management token used for authentication in the examples:
- Guide for users with a Yandex account.
- Guide for a service account.
- How to get a token for a federated account.
-
Get the ID of the folder.
-
Get information about the image to create your VM 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 \ --header "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.
-
-
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=b1gvmob95yys******** curl \ --header "Authorization: Bearer ${IAM_TOKEN}" \ "https://vpc.api.cloud.yandex.net/vpc/v1/subnets?folderId=${FOLDER_ID}"
Result:
{ "subnets": [ { "v4CidrBlocks": [ "10.130.0.0/24" ], "id": "b0c6n43ftldh********", "folderId": "b1gvmob95yys********", "createdAt": "2018-09-23T12:15:00Z", "name": "default-ru-central1-a", "description": "Auto-created default subnet for zone ru-central1-a", "networkId": "enpe3m3faglu********", "zoneId": "ru-central1-a" }, ... ] }
-
Create a file with the body of the request to create a VM, e.g.,
body.json
:{ "folderId": "b1gvmob95yys********", "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": "fd8rc75pn12f********" } }, "networkInterfaceSpecs": [ { "subnetId": "b0c6n43ftldh********", "primaryV4AddressSpec": { "oneToOneNatSpec": { "ipVersion": "IPV4" } } } ] }
Where:
-
folderId
: Folder ID. -
name
: Name the VM will get when created. -
zoneId
: Availability zone matching the selected subnet. -
platformId
: Platform. -
resourceSpec
: Resources available to the VM. The values must match the selected platform. -
metadata
: In metadata, provide the public key for accessing the VM via SSH. For more information, see VM metadata. -
bootDiskSpec
: Boot disk settings. Specify the selected image ID and disk size.You can also view image IDs in the management console
when creating a VM or on the image page in Cloud Marketplace, under Product IDs.The disk size must not be less than the minimum value specified in the image details.
-
networkInterfaceSpecs
: VM's network interface settings.-
subnetId
: ID of the selected subnet. -
primaryV4AddressSpec
: IP address to assign to the VM. To add a public IP address to your VM, specify:"primaryV4AddressSpec": { "oneToOneNatSpec": { "ipVersion": "IPV4" } }
To add multiple network interfaces to a VM, provide an array with the required number of objects containing network interface settings in the
networkInterfaceSpecs
parameter. You can add up to eight network interfaces to a single VM. -
Read more about the request body format in the API reference.
-
-
Create a VM:
export IAM_TOKEN=CggaATEVAgA... curl \ --request POST \ --header "Content-Type: application/json" \ --header "Authorization: Bearer ${IAM_TOKEN}" \ --data '@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.