Skip to main content
Before you start, ensure that you have API Key with Instances -> Read and write permission

​
Checking GPU Availability

First, check available GPU configurations: 
prime availability list
Filter results using these options:
  • --gpu-type: Specific GPU model (e.g., H100_80GB)
  • --regions: Geographic locations (e.g., united_states,canada)
  • --gpu-count: Number of GPUs needed
  • --socket: Socket type (PCIe, SXM4, etc.)
  • --provider: Name of a provider

​
Creating an Instance

Create a new instance interactively: 
prime pods create

​
Available Options

​
--id
string
Short ID from availability list
​
--cloud-id
string
Cloud ID from provider
​
--gpu-type
string
GPU model (e.g., H100_80GB, A100)
​
--gpu-count
integer
Number of GPUs required
​
--name
string
Instance name (alphanumeric and dashes only)
​
--disk-size
integer
Storage size in GB
​
--vcpus
integer
Number of virtual CPUs
​
--memory
integer
RAM in GB
​
--image
string
Operating system image
​
--team-id
string
Team identifier for the instance
​
--env
string
Environment Variable in form KEY=value - this can be used multiple times
​
--disks
string
Attach existing disk IDs to the instance. Can be specified multiple times for multiple disks.
  • Example: --disks disk-id-1 --disks disk-id-2

​
Interactive Creation Process

If options are not provided, the CLI will guide you through:
  1. GPU Selection
  2. Configuration Options
  3. Resource Allocation
  4. Image Selection
  5. Team Assignment
The CLI will show default values and valid ranges for resources like disk size, vCPUs, and memory based on the selected GPU configuration.

​
Using Custom Templates

To use a custom environment:
  1. Select a template from the Templates Page
  2. Create instance with template:
prime pods create \
  --image custom_template \
  --custom-template-id "template_id"
Ensure your template is compatible with the selected GPU configuration.

​
Attaching Persistent Disks

To attach existing persistent disks to your instance: 
prime pods create \
  --id 346663 \
  --disks disk-id-1 \
  --disks disk-id-2
This is useful for:
  • Accessing shared datasets across multiple instances
  • Persisting model checkpoints and training artifacts
  • Resuming training from previous sessions
Use prime disks list to see your available disks and their IDs. Learn more about creating and managing disks in Managing Disks.

​
Managing Your Instance

Monitor instance status: 
prime pods status <pod-id>
SSH into your instance: 
prime pods ssh <pod-id>
Configure your SSH key path in CLI settings and run chmod 400 on your private_key.pm before using SSH.
Terminate instance: 
prime pods terminate <pod-id>
You’ll be prompted to confirm before termination.