Aim Virtual Machine

Last update: July 28 2026

Aim Virtual Machine is a pre-configured cloud server with a tool for tracking machine learning (ML) experiments. The tool allows you to compare models, analyze metrics, and manage ML experiments.

The image from which the server is deployed contains:

• Aim — a tool for tracking ML experiments;

• Docker — a platform for running containerized applications;

• Docker Compose — a tool for running multi-container applications in Docker;

• nginx — a web server and reverse proxy;

• drivers required for working with graphics processing units (GPU).

Before creating a server, please review the software license agreements included in the image.

Functional capabilities

• experiment logging — recording metrics, hyperparameters, and artifacts throughout the model training process;

• visualizing experiment results and comparing data via the Aim UI web interface.

Minimum resource requirements

Number of vCPUs	2
RAM	4 GB
Boot volume	20 GB
GPU	Not required

Start working with Aim Virtual Machine

1. Create a cloud server with Aim.

2. Run Aim.

1. Create a cloud server with Aim

1. In the Control panel, on the top menu, click Products and select AI Marketplace.

2. Click Create server.

3. Fill in the blocks:

   • Name and placement;
   • Source;
   • optional: GPU;
   • Configuration;
   • Disks;
   • Network;
   • optional: Access;
   • optional: Additional settings;
   • optional: Automation.

4. Check the server price.

5. Click Create server.

Name and placement

1. Enter the server name.

2. Select a location where the server will be created. The available GPU list depends on the location. You cannot change the location after the server is created.

Source

Select an image Aim VM (Ubuntu 24.04 LTS 64-bit).

Optional: GPU

1. Click Add GPU.

2. Select the GPU type. When choosing a GPU, consider the minimum resource requirements for the image. GPU specifications and descriptions can be found in the Graphics Processors (GPU).

3. Specify the number of GPUs.

After the server is created, you will be able to change the GPU type and quantity or delete the GPU. Learn more in the Change Cloud Server Configuration.

Configuration

1. Specify the number of vCPUs.

2. Specify the RAM size.

After the server is created, you will be able to change the configuration.

Disks

1. Select the boot disk type. GPUs are not available when using a local disk as a boot disk.

2. Specify the disk size in GB or TB. The maximum size for all network volumes is 10 240 GB (10 TB), for a local disk — 1 256 GB (1 TB).

3. If you selected the SSD Universal v2 or SSD Fast v2 disk type, specify the total number of read and write operations in IOPS. After the volume is created, you can change the IOPS value by increasing or decreasing it. The number of IOPS changes is unlimited.

4. Optional: to add additional disks:

   4.1. Click Add volume.

   4.2. Select the volume type.

   4.3. Specify the disk size in GB or TB. The maximum size for all network volumes is 10 240 GB (10 TB), for a local disk — 1 256 GB (1 TB).

   4.4. If you selected the SSD Universal v2 or SSD Fast v2 disk type, specify the total number of read and write operations in IOPS. After the volume is created, you can change the IOPS value — decrease or increase it. The number of IOPS changes is unlimited.

   After the server is created, you will be able to detach additional volumes from it or attach new ones.

Network

You can add the server to a new or existing subnet. The subnet can be:

• private without internet access. You will not be able to connect to the server from the internet, including via SSH or RDP;
• private with a single public IP address. A static public IP address connects to the private server address via a cloud router. The server will be accessible from the internet via this public IP address;
• public, where all addresses are accessible from the internet.

Private subnetwork without internet access

1. To add an existing private subnetwork:

   1.1. In the Subnet field, select an existing subnet.

   1.2. Optional: change the default private IP address of the server.

2. To add a new private subnetwork:

   2.1. In the Subnet field, select the Private subnet type.

   2.2. Optional: change the subnetwork CIDR.

   2.3. Optional: enable the DHCP toggle. Learn more about the DHCP protocol in the Selectel blog article Principles of the DHCP Protocol.

   2.4. Optional: change the default gateway IP address.

   2.5. Optional: change the network in which the subnet will be created — you can select an existing network or create a new one. If you are creating a new network, enter the network name.

Private subnetwork with a public IP address

1. If you already have a private subnetwork and a cloud router with internet access:

   1.1. In the Subnet field, select the Private + 1 public IP subnet type.

   1.2. In the Private field, select an existing subnet.

   1.3. Optional: change the default private IP address of the server.

2. If you do not have a private subnet or a cloud router with internet access, in the Subnet field, select the Private + 1 public IP subnet type.

   A private network nat, a router router-nat, and one public address will be created automatically. The server will be connected to the subnet in the nat.

Public subnetwork

1. To add an existing public subnetwork:

   1.1. In the Subnet field, select an existing subnet.

   1.2. Optional: change the default public IP address of the server.

2. To add a new public subnetwork:

   2.1. In the Subnet field, select the Public subnet type.

   2.2. In the Subnet size field, select the subnet size.

Optional: Access

1. In the Password for «root» field:

   1.1. Copy the password for the root user — the user with unrestricted system privileges.

   1.2. Save the password in a secure place and do not share it in plain text.

2. Add an SSH key for the project to the server for secure connection:

   2.1. If the SSH key is not added to the cloud platform, click , enter the key name, paste the public key in OpenSSH format, and click Add.

   2.2. If the SSH key is added to the cloud platform, in the SSH key field, select an existing key.

Optional: Additional settings

1. To create a preemptible server, check the Preemptible server checkbox.

2. If you are planning to create several servers and want to increase infrastructure fault tolerance, add the server to a placement group:

   2.1. To create a new group, click , enter the group name and select a placement policy for different hosts:

   • preferred — the system will try to place servers on different hosts. If there is no suitable host available when creating a server, it will be created on the same host;

   • mandatory — servers in the group must be located on different hosts. If there is no suitable host available when creating a server, the server will not be created.

   2.2. If the group is created, in the Placement group field, select a placement group.

3. To add additional information or filter servers in the list, add server tags. An image name tag is added automatically. To add a new tag, enter it in the Tags field.

Optional: Automation

1. To add a script to be executed by the cloud-init agent during the first system boot, in the User data field:

   • open the Text tab and paste the script as text;
   • or open the File tab and upload the script file.

   For examples of scripts and supported formats, see the User data guide.

2. Launch Aim

1. In the control panel, on the top menu, click Products and select AI Marketplace.

2. In the Aim Virtual Machine card, click Go to GUI.

3. Enter the username — admin.

4. Enter the password—the server UUID. You can copy it in the control panel: in the top menu, click Products → AI-marketplace → in the menu of the server, select Copy UUID.

5. Click Log in.