Delete an instance

Deleting an instance permanently removes it and its workspace disk, and stops billing for both. Its saved images, datasets, SFS, PFS, and reserved IPs stay in the project for you to use again. As you delete it, you can also keep its public IP as a reserved IP.

Before you begin

• Permission to delete instances in the project. Every project role except MEMBER has it; a MEMBER needs a policy that allows deleting instances.
• An instance in any status except Saving Image. Wait for an image save to finish first.
• Copies of any files you need from /home/jovyan. See Copy files to and from an instance.

If you recently attached a VPC IP to the instance, wait until it has finished connecting. The delete is refused while the VPC IP is still connecting.

To keep the installed packages for later, save the instance as an image while it is Running. Saved images stay after the instance is deleted.

Delete the instance

Deleting an instance permanently deletes its workspace at /home/jovyan with everything in it.

1. Open the instance’s actions menu, from its row or its own page, and select Delete.
2. (Optional) To keep the instance’s public IP, tick Reserve the instance’s IP. The IP stays in the project as a reserved IP that you can attach to another instance, and it has a monthly charge; for prices, see E2E’s pricing page. You can do this when the instance has a public IP and you have permission to create reserved IPs.
3. Tick the box that confirms you want to delete the instance, and select Delete.

Billing for the instance and its workspace stops, and TIR emails you that the instance was deleted.

If the delete is refused, for example because your account already holds as many reserved IPs as it can, see Stop or Delete does not work.

What stays after you delete

These outlive the instance and are billed as their own products until you delete them:

• Saved images stay in the Container Registry.
• Datasets, SFS, and PFS are unmounted and keep their data, ready to mount on another instance.
• Reserved IPs attached to the instance are detached and stay reserved in the project.

On a private cluster, the instance’s local storage is detached, and you can attach it to another instance when you create it. Local NVMe storage from the instance’s plan, at /mnt/local, is deleted with the instance, like the workspace. An attached VPC IP is detached, and alerts attached to the instance are removed with it.

Delete a committed instance

You can delete a committed instance during its term, but the days left are not refunded. To have a committed instance deleted when its term ends instead, choose Auto deletion of this committed machine as its renewal preference; see Change the plan of an instance.

Delete an instance that is Pending

While an instance is Pending, its menu offers Revoke Request instead of Delete. Revoking deletes an instance that has never run. An instance that has run before is stopped instead. Its workspace is billed until you delete the instance, which you can do once it is Stopped.

Start again from a saved image

To start again with the same packages, launch a new instance from a saved image; see Create an instance from your own image. Delete the saved images, datasets, file systems, and reserved IPs you are finished with where you manage each one. Deleting them ends their charges.

You can also delete an instance through the TIR API’s Delete Instance / VM operation.