Skip to main content

Managing Instances

Once the instance is created, you can navigate to Manage Instances to access:

  • Overview: User can see the Instance, Plan and Connection Details under the Overview tab.

  • Node Events: Entry logs for seeing the instance specific action like Starting Container, Pulling Image

NodeEvents

  • Monitoring: The Monitoring tab provides real-time insights into workspace, storage, and memory usage. It also tracks GPU utilization, memory consumption, temperature, and power usage to help users monitor the performance of their instance

  • Workspace size: You can view the current disk size and modify it based on your requirements. To update, adjust the disk size value and click the Update button.

  • Associated Datasets: In this section, users can attach datasets to the instance in both mounted and unmounted modes. After updating a dataset, the instance must be restarted for the changes to take effect.

  • Shared File-System: It is built to deliver simple, scalable, and highly available file storage, allowing multiple instances to access the same file system simultaneously for seamless shared storage. For this the SFS must be mounted to a path.

  • Network and Security: Under the Network & Security tab, users can configure SSH keys, attach or detach a reserved IP, manage Security Groups, and attach custom scripts to the Node. When a Security Group is added, the corresponding custom ports are automatically configured. The attached script ensures seamless execution by installing and configuring all required dependencies for optimal performance.
    VPC IP : You can attach a Reserved VPC IP to your instance to enable private connectivity with a VPC created in MyAccount.

    Attach: To enable Attach VPC IP, select a reserved VPC IP, and click Attach.
    Detach: To dettach click Detach VPC IP and confirm the action.

Note

Only one VPC IP can be attached to an instance at a time.


For more information on reserving and managing VPC IPs, click here.

Connection Status

After attaching a VPC IP, the instance will not establish connectivity until the status changes to “Connected.”
Once connected, the instance will display its Inbound and Outbound private IP addresses.

Inbound IP Behavior : The Inbound private IP is used to access this instance from within MyAccount through the connected VPC.

  You can SSH or connect to this node using its Inbound private IP.
  Any MyAccount node attached to the same VPC can reach this instance through its Inbound IP.

Outbound IP Behavior : The Outbound private IP is used when this instance sends traffic to other nodes inside the same VPC.

  All outbound requests from this instance will originate from its Outbound private IP.
  Communication is permitted only to nodes within MyAccount that are part of the same VPC.

  • Images: Here, you can save the instance image to the container registry. Saving an image allows you to preserve the current environment (packages, configurations, and code) so it can be reused, replicated, or restored later.

Instance Actions​

  • Launch App: This provides an interactive workspace where you can manage files, write and execute code, and create documentation. Example Use Case- If a user wants to verify the GPU resources of their launched H100 series instance, they can run the command "nvidia-smi" inside a Python3 kernel.

LaunchApp

  • Save Image: The Save Image option lets you capture the current state of your instance (packages, configs, and code) for reuse and reproducibility. To save an image, you must have a container registry created beforehand

  • Restart: Restarting clears the current session while preserving the saved data and settings, ensuring instance runs with the updated state.

  • Update Plan: After clicking the Update Plan button, the user is redirected to the Update Node Resource page, where they can choose the desired GPU/CPU plan for their Instance Image. Once they click Update, the instance will enter a Waiting status, and shortly after, it will be updated with the new resources and return to Running status.

Note

For updating the Instance node should be in the stopped state. Click on the Stop Instance from Action button.

Update Plan​

Follow these recommended steps to safely update the plan of your instance:

  1. Create a Save Image (Backup)

    • Ensure the instance is in a Running state
    • Navigate to the instance details page
    • Click Save Image and wait for the operation to complete

  2. Stop the Instance

    • Stop the instance from the console once the save image is created

Action screenshot

  1. Update the Instance Plan
    • Selectt the instance and click Update Plan
    • Choose the desired GPU/CPU plan and click Confirm
    • The instance will enter Waiting status temporarily and switch back to Running upon completion

Action screenshot

  1. Apply Saved Image (If Required)
    • Once the instance is back to Running, restore the previously created save image if required
note
  • Creating a Save Image ensures rollback capability if anything goes wrong
  • Instance must be in a Stopped state before updating the resources
  • Once upgraded, attached workspace volumes remain available and intact
  • Always verify instance health after the plan upgrade

Delete: When instance is deleted, all the resource associated with it will be deleted, including the worskpace(disk).