Yandex Compute Cloud

Getting started
Step-by-step instructions
- All instructions
- Creating VMs
- DSVM
  - Overview
  - Creating a VM from a public DSVM image
- Placement groups
- Images with pre-installed software
- Getting information about a VM
  - Getting information about a VM
  - Viewing serial port output
- Managing VMs
- Working on VMs
- Creating new disks
  - Creating an empty disk
  - Create an empty disk with a large block
- Disk management
- Creating new images
  - Uploading your image
- Managing images
  - Deleting a disk image
- Managing the serial console
- Creating instance groups
- Getting information about instance groups
- Managing instance groups
- Dedicated hosts
  - Creating a VM in a group of dedicated hosts
  - Creating a VM on a dedicated host
Yandex Container Optimized Solutions
Scenarios
- Configuring NTP time synchronization
- Running instance groups with auto scaling
Concepts
- Relationship between resources
- Virtual machines
- Disks
  - Overview
  - Disk snapshots
- Images
- Instance groups
- Dedicated host
- Backups
- Quotas and limits
Access management
Pricing policy
- Current pricing policy
- Archive
Compute API reference
- Authentication in the API
- gRPC
- REST
  - Overview
  - Disk
  - DiskPlacementGroup
  - DiskType
  - HostGroup
  - HostType
  - Image
  - Instance
  - PlacementGroup
  - Snapshot
  - Zone
  - Operation
    - Overview
    - get
  - InstanceGroup
Questions and answers

Allocation policy

When creating an instance group, you can choose the Yandex.Cloud regions and availability zones to host your instances.

A region is a specific geographic location where you can deploy instances. Each region consists of one or more zones. Only one region is currently available. More about the geo scope of Yandex.Cloud.

Region	Zones	Location
`ru-central1`	`ru-central1-a` `ru-central1-b` `ru-central1-c`	Vladimir region, Moscow region, and Ryazan region.

You can't move instances to other availability zones, but you can update a group with new zone values.

The allocation policy is defined in the allocation-policy key in the YAML file. The value can be the list of zones defined in the zones key. You can specify any available zones to evenly distribute the group instances across.

Example of a YAML file entry:

...
allocation_policy:
    zones:
        - zone_id: ru-central1-a
        - zone_id: ru-central1-b
        - zone_id: ru-central1-c
...

Keys:

Key	Value
`zones`	Zone list. Each zone is defined in the `zone_id` key as a `key-value` pair.
`zone_id`	Zone ID.