Skip to main content
This guide explains each part of creating a Compute instance. It covers the organization context, resource and software choices, connection settings, price review, and the first connection after launch.

​
What you’ll need

  • A Compute account with access to an organization
  • Enough credits in the organization balance
  • An SSH public key if you want terminal access
  • A general idea of the hardware, software, and network access your workload needs

​
Before you create the instance

Check the organization shown in the upper-left corner of the console. The instance will use that organization’s balance and access rules.
  • Owners can add credits and manage organization billing.
  • Admins can create instances and view all organization instances, but cannot add credits.
  • Members can create instances using the shared balance and see the instances they created.
If the organization does not have enough credits, ask its Owner to add more. Admins and Members cannot add credits themselves.

​
Choose between a container and virtual machine

Select Create from the left sidebar, then choose the resource type you want to launch.

​
Container

Choose a container when you want a prepared application environment and do not need control of the full operating system. Templates can provide an operating system, drivers, libraries, and development tools.

​
Virtual machine

Choose a virtual machine when your workload needs a full operating system or broader system-level control. See Choosing between a virtual machine and a container for help deciding.

​
Configure the instance

1

Choose a location

Select an available location for the instance.Consider where your users, services, and data are located. A nearby location can reduce network latency. Configurations marked as sold out cannot be selected until capacity becomes available.
2

Choose your setup

Select GPU or vCPU only, then choose the available resource profile and size.The console shows the main specifications for each option, including:
  • GPU count and model, when applicable
  • vCPU allocation
  • GPU memory and system memory
  • Disk space
  • Network bandwidth
  • Active price
Use the smallest configuration that meets the workload’s memory and performance needs. You can create another instance later if you need a different setup.
3

Pick a template or operating system

For a container, choose one of the available templates or select the option to create a new custom template.For a virtual machine, choose the operating-system image you want to install.Review the image details before continuing. A template may already include drivers, libraries, notebook software, or workload-specific tools.
4

Set up connection options

Choose how you’ll access the instance.SSHCompute uses a public SSH key to authorize terminal access. The key saved to your account may appear automatically. Select Edit if you need to replace it before creating the instance.HTTPSEnable HTTPS when the workload needs a secure browser-accessible or API endpoint.TCP and UDPEnable the protocol required by your service. Leave these options off when the workload does not need inbound access over them.Jupyter NotebookEnable Jupyter Notebook when the option is available and you want notebook access in a browser. The access link appears in the instance’s connectivity details after launch.
Some connection settings are permanent after creation. Confirm the protocols and access methods you need before continuing.
5

Name the instance

Enter a name that follows the rules shown in the console. Instance names generally use letters, numbers, and dashes without spaces or special characters.A descriptive name makes the instance easier to identify later, especially when several people are creating resources in the same organization.
6

Review the setup and estimated cost

The review section summarizes:
  • Location
  • Resource type and size
  • Template or operating system
  • Memory, disk, and bandwidth
  • Connection options
  • Estimated hourly, daily, and weekly cost
Review the active price and make sure the selected organization has enough credits.
The hourly, daily, and weekly values help you estimate spending. Eligible Compute usage is charged per second after the instance reaches Running.
7

Create the instance

Select the button to create the container or virtual machine.The instance appears on the Instances page while Compute prepares it. Wait until its status changes to Running before trying to connect.
Preparation usually takes a few minutes. Charging begins when the instance is running, rather than while the creation form is open.

​
Connect over SSH

After the instance reaches Running:
  1. Open Instances.
  2. Select the running instance.
  3. Open its connectivity details.
  4. Copy the SSH command shown by the console.
  5. Run the command in your terminal.
A typical command looks like this:
The exact username and address depend on the selected template or operating system. Use the private key that matches the public key supplied during creation.
After a successful connection, you can add the host and identity file to ~/.ssh/config to make later connections shorter.
For platform-specific instructions, see:

​
Connect through Jupyter or a public endpoint

When you enabled Jupyter Notebook, HTTPS, TCP, or UDP during creation, open the instance’s connectivity details to find the available address or access link. If a service is not reachable:
  • Confirm that the required connection option was enabled.
  • Check that the application is listening on the expected interface and port.
  • Review any firewall rules inside the container or virtual machine.
  • Make sure the instance is still running.

​
Understand who can see the instance

The person who creates an instance can see it in their instance list.
  • Owners and Admins can see all instances created within the organization.
  • Members see the instances they created.
  • Usage is charged to the organization balance, regardless of who created the instance.
See How organizations work in Compute for the full role comparison.

​
Stop or terminate the instance

When you finish working:
  • Stop the instance to pause compute charges and preserve it temporarily for a later start.
  • Terminate the instance when you no longer need it or its local data.
Termination permanently deletes the instance and its local data. Download important files before you terminate it.
See How to stop or terminate a Compute instance for the lifecycle details.

​
If creation is blocked by the balance

The review section tells you when the organization needs more credits.
  • If you are the Owner, open Billing and add credits.
  • If you are an Admin or Member, ask the organization Owner to add credits.
After the balance updates, return to the creation form and review the configuration again before launching.

​
See also