Instance Templates
info
Crusoe Cloud is currently in private beta. If you do not currently have access, please request access to continue.
Instance Templates offer an easy way to save commonly-used VM configurations across your organization or project. Templates may then be used to atomically create multiple VMs that are identically configured.
How Instance Templates work
You can create one or more templates in your project that allow you to specify and save the following attributes associated with VM creation.
Field Name | Description |
---|---|
Instance Type | The type of instance you want to create (e.g.: l40s-48gb.10x, h100-80gb-sxm-ib.8x, etc.). |
Location | The location where your VMs must be created (e.g.: us-east1-a). You may also choose to create a 'Global' template. Global templates allow you to re-use the same template across different locations. Region-specific attributes, like InfiniBand network IDs, during VM creation. Location must be specified during VM creation for global templates. |
Image Name and Version | The image name and version to be used for VMs created from the template (e.g.: ubuntu22.04-nvidia-pcie-docker:latest) |
Disks to Create | Templates allow you to create one or more persistent disks of specified sizes that will be attached to VMs created from the template. Currently, attaching existing disks is not supported via templates. |
VPC Network and Subnet | The VPC network and subnet to place VMs in. For global templates, this defaults to the default VPC and subnet in the region selected during VM creation from the template. |
InfiniBand Network and Partition | The IB network or partition to place VMs in. Must be specified during VM creation for global templates. Only required for IB-enabled VMs. |
Public SSH Key | The SSH key used to connect to VMs. |
Lifecycle Scripts | Startup and Shutdown scripts that will be applied to VMs created from the template. |
Reservation ID | The ID of the reservation to be used when creating a VM using the template. |