Skip to main content

Actions

Manage your instance lifecycle and configuration through these available actions:

Launch App​

The Launch App action opens the application interface running on your instance directly in the browser, such as a Jupyter notebook, or any other service exposed on your instance.

Stop​

The Stop action shuts down your instance and releases its compute resources. Your saved data and configurations are preserved and will be available when you start the instance again.

When to Use​

  • When you no longer need the instance running temporarily and want to free up compute resources.
  • When you want to pause billing for compute without deleting the instance or its data.

How to Stop​

  1. Navigate to your instance and click Stop from the Actions menu.
  2. Confirm the action when prompted.
  • Only hourly instances can be stopped.
  • Billing Note: Stopping an instance pauses compute billing but does not stop billing for the workspace disk. Disk charges continue until the instance is deleted.
  • Files saved within /home/jovyan will be preserved. However, any packages manually installed during the session will need to be reinstalled when the instance is started again.

Start​

The Start action resumes your instance by allocating compute resources and re-establishing the connection to the workspace. It is the opposite of the Stop action.

When to Use​

  • When you have stopped your instance and want to resume work.

How to Start​

  1. Navigate to your stopped instance and click Start from the Actions menu.
  2. Confirm the action when prompted.

Restart Instance​

The Restart action refreshes your instance while preserving your saved data and configurations. It clears the current session and applies any updated settings.

When to Use​

  • When the instance is unresponsive or experiencing performance issues.
  • After making system-level configuration changes that require a reboot.
  • When start scripts need to be re-executed.
  • When you need a fresh session without losing your saved work.

How to Restart​

  1. Navigate to your instance and click Restart from the Actions menu.
  2. Confirm the restart when prompted.

Files saved within /home/jovyan will be preserved after the restart. However, any packages manually installed during the session will need to be reinstalled after the instance restarts.


An instance can be started, stopped, or restarted using the same API endpoint. Refer to the Instance Actions API documentation for request parameters and examples.

Attach VPC​

The Attach VPC action connects your instance to a Virtual Private Cloud network, enabling private networking between instances and other resources within the same VPC. For more info, refer to the VPC documentation.

Save Image​

Captures a snapshot of your instance including:

  • Installed packages and libraries
  • Configuration files
  • Custom code and scripts

This allows you to recreate the exact same environment later or share it with your team. For more info follow the Save Image documentation.

Update Image​

The Update Image action allows you to replace the current image running on your instance with a different one, without creating a new instance. This is useful when you need to switch frameworks, upgrade to a newer environment, or change your software stack while retaining your instance configuration.

To update the image of the instance, follow this guide: Update Image.

Update Plan​

The Update Plan action allows you to change your instance's GPU or CPU configuration to scale resources up or down based on your workload requirements.

To upgrade the configuration of the instance, follow this guide: Update Plan.

Convert to Committed​

The Convert to Committed action allows you to switch an instance from an hourly billing plan to a committed pricing plan, which offers a lower rate in exchange for a fixed-term commitment.

When an instance is converted to a committed plan, the resources are reserved for the selected commitment period and billing is applied according to the committed pricing terms. This action is permanent, meaning the instance cannot be reverted back to the hourly plan once the conversion is completed.

However, you can modify the post-commitment policy associated with the instance. For more information, see Post-Commitment Options.

Delete​

Permanently removes the instance and all associated resources, including:

  • The instance itself
  • Attached workspace (disk storage)
info

If instance is deleted, then other attached resources will not be deleted such as attached Datasets, SFS, PFS, Reserve IPs.

An instance can be deleted using an API request. Refer to the Delete Instance API documentation for request parameters and examples.


Permanent Action

This cannot be undone. Deleting a node deletes its workspace. Back up any files you want to keep to EOS buckets or your local machine before deletion.

Reserve IP on Deletion​

When deleting an instance, you have the option to reserve the IP address for ₹199.

Why reserve your IP?

  • Maintains business continuity
  • Applications and integrations continue working without reconfiguration
  • Prevents downtime from IP address changes
  • Keeps the same trusted IP address for security and compliance
  • Provides flexibility to reattach the IP to a new instance later

This small investment preserves a critical network asset and saves time managing IP changes across your infrastructure.