A VM with a public floating IP and a data volume, locked down with a security group (only SSH and HTTPS in) and captured to a fresh image nightly by an image schedule. Reuses client and the real folder_id / subnet_id from the Networking example.

As a single transaction

The same stack created atomically. Everything created here gets a client-generated ULID so the VM and volume attachment can reference resources that don't exist yet:

Volume backup and restore

The same backup flow over the SDK: client.images captures a volume-sourced image, and a second client.volumes call restores it. volumeId and vmId are mutually exclusive on the image, as are imageId and osImageId on the volume.

Related pages

Resource docs

• VM resource docs
• Volume resource docs
• Volume Attachment resource docs
• Floating IP resource docs
• Security Group resource docs
• Image Schedule resource docs
• SSH Key resource docs
• Transaction resource docs

More in this section

• IAM
• Networking
• VPN
• Load Balancing
• Kubernetes
• S3
• Valkey
• Valkey Replication
• PostgreSQL
• Kafka
• ClickHouse
• OpenSearch
• GitLab
• Examples

Reference

• Interactive API reference (Swagger)