Creating a VM from a Windows public image
This section provides guidelines on how to create a VM with the Windows OS. To create a Linux-based VM, follow the instructions Creating a VM from a public Linux image.
To use Microsoft products, you must provide correct user data.
To create a VM:
-
In the management console
, select the folder to create the virtual machine in. -
In the list of services, select Compute Cloud.
-
At the top right, click Create VM.
-
Under Basic parameters:
-
Enter a name and description for the VM. The naming requirements are as follows:
- 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.
-
-
Under Image/boot disk selection, select an image and a Windows-based operating system.
-
(Optional) Under Disks, select the Disks tab and configure a boot disk:
-
Select disk type.
-
Specify the desired disk size.
If you want to create a VM instance from an existing disk, under Disks, add a disk:
-
Click Add disk.
-
Enter the disk name.
-
Select disk type.
-
Specify the desired block size.
-
Specify the desired 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.
-
-
-
Under Computing resources:
- Choose a platform.
- Specify the guaranteed share and the required number of vCPUs, as well as the amount of RAM.
- Make your VM preemptible, if required.
- (Optional) Enable a software-accelerated network.
-
Under Network settings:
-
Enter a subnet ID or select a cloud network from the list.
If you do not have a network, click Create network to create one:- In the window that opens, enter the network name and specify the 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
-
In the Public IP field, choose a method for assigning an IP address:
Auto
: Assign a random IP address from the Nebius Israel IP pool.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.
-
In the Internal IPv4 address field, select the method for assigning internal addresses:
Auto
orManual
. -
(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.
-
Select the appropriate security groups.
-
-
Under Access, specify the data required to access the VM:
- (Optional) Select or create a service account. With a service account, you can flexibly configure access rights for your resources.
- If required, grant access to the serial console.
-
(Optional) Under Placement, select a VM placement group.
-
Click Create VM.
The virtual machine will appear in the list. When a VM is created, it is assigned an IP address and hostname (FQDN). You can use this data to access the VM via RDP.
If you don't have the Nebius Israel 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 for creating a VM:
yc compute instance create --help
-
Select one of the public images on Windows.
To get a list of available images using the Nebius Israel 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 | dqni65lfhvv2den5gtv9 | READY | | fdv7ooobjfl3******** | windows-2016-gvlk-1548913814 | windows-2016-gvlk | dqnnc72gj2ist3ktjj1p | READY | | fdv4f5kv5cvf******** | ubuntu-1604-lts-1549457823 | ubuntu-1604-lts | dqnnb6dc7640c5i968ro | READY | ... +----------------------+-------------------------------------+--------------------------+----------------------+--------+
-
Create a VM in the default folder:
yc compute instance create \ --name second-instance \ --zone il1-a \ --public-ip \ --create-boot-disk image-folder-id=standard-images,image-family=windows-2016-gvlk
This command creates a VM instance with the following characteristics:
- Named
second-instance
. - With the Windows Server 2016 OS.
- In the
il1-a
availability zone. - With a public IP address.
To create a VM without a public IP, remove the
--public-ip
flag.Specify:
-
The VM name in the
--name
flag.The name must be unique within the folder. It may contain lowercase Latin letters, numbers, and hyphens. The first character must be a letter. The last character cannot be a hyphen. The name may not be longer than 63 characters.
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.
- Named
Create a VM using the create REST API method for the Instance resource:
-
Get an IAM token for authentication in these examples:
- Instructions for a service account.
- Instructions for a federated account.
-
Get the ID of the folder.
-
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=windows-2016-gvlk curl -H "Authorization: Bearer ${IAM_TOKEN}" \ "https://compute.api.il.nebius.cloud/compute/v1/images:latestByFamily?folderId=standard-images&family=${FAMILY}" { "productIds": [ "f2eu62v659or2tqv28l0" ], "os": { "type": "WINDOWS" }, "id": "fd85s1nlcavgdpc16hj3", "folderId": "standard-images", "createdAt": "2019-04-30T10:53:56Z", "name": "windows-2016-gvlk-1556619485", "description": "Windows Server 2016 Datacenter is a operating system for virtualized private cloud environments. This version is activated with GVLKs. Website and documentation: https://www.microsoft.com/en-us/cloud-platform/windows-server", "family": "windows-2016-gvlk", "storageSize": "26344423424", "minDiskSize": "26843545600", "status": "READY" }
- To learn more about the image, see the list of public images.
- If you know the image family, get information about the latest image in this family:
-
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.il.nebius.cloud/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-il1-a", "description": "Auto-created default subnet for zone il1-a", "networkId": "enpe3m3fagludao8aslg", "zoneId": "il1-a" }, ... ] }
-
Create a file where the body contains your request for VM creation (for example,
body.json
):{ "folderId": "b1gvmob95yysaplct532", "name": "instance-demo-no-pwauth", "zoneId": "il1-a", "platformId": "standard-v3", "resourcesSpec": { "memory": "4294967296", "cores": "2", }, "bootDiskSpec": { "diskSpec": { "size": "26843545600", "imageId": "fd85s1nlcavgdpc16hj3" } }, "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.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.
-
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.il.nebius.cloud/compute/v1/instances
If you do not have Terraform yet, install it and configure the Nebius Israel provider.
-
In the configuration file, describe the parameters of the resources you want to create:
resource "yandex_compute_instance" "vm-1" { name = "windows-vm" allow_stopping_for_update = true platform_id = "standard-v3" zone = "<availability_zone>" resources { cores = <number_of_vCPU_cores> memory = <amount_of_RAM_in_GB> } boot_disk { initialize_params { image_id = "<image_ID>" } } network_interface { subnet_id = "${yandex_vpc_subnet.subnet-1.id}" nat = true } } 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_instance
: Description of the VM: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.resources
: 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, setnat = true
.
yandex_vpc_network
: Description of the cloud network.yandex_vpc_subnet
: Description of the subnet your virtual machine will connect 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 on resources that 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 that the resources are there and their settings are correct using the management console
. -
Note
It usually takes up to 6 minutes to start a VM and initialize Remote Desktop (RDP). In rare cases, loading may take much longer than the time specified. For example, when using:
- VMs with less than 100% guaranteed vCPU performance.
- VMs that generate a load that exceeds the boot disk's IOPS limit.
- Network HDD drives with small storage capacity.
Reset the administrator password once the VM is created.
You can make a public IP address static. For more information, see Making a VM's public IP address static.