Manage your Workbench

Workbench Manage Status Page

The Manage Status page within the Workbench section offers users a centralized interface for monitoring and controlling both active and previously launched workbenches.

Key Features and Layout

Workbenche Tables: The table displays a list of all launched workbenches, with the following columns:

Field	Description
Name	The type of environment (e.g., Jupyter Notebook, RStudio).
Description	User-provided context for the session.
Status	Current state of the workbench, can be `Creating`, `Running`, `Stopped`, or `Terminated`.
Last Updated	The timestamp of the most recent state change.
Date Created	The date when the workbench was initially launched.
Owner	The user who initiated the instance.
Password	An eye icon appears if a generated access password is available (e.g., for tools like RStudio).
Options Menu	An action menu available for each entry. (⋮)

Available Actions

Using the three-dot Options menu on the right, users can perform the following actions:

Action	Description
Open	Connect to the running environment, which redirects the user to the notebook or application interface via the proxy/load balancer.
Stop	Gracefully shut down the instance, preserving disk storage and incurring no compute charges after stopping.
Terminate	Permanently delete the instance. This includes the cleanup of all related metadata and storage. This action is irreversible.

Stop your Workbench

You can restart this workbench with all storage and installed packages intact. This action is a great way to pause your work while reducing compute costs.

Managing Workbench Cost

Workbench Status	Compute Charges	Storage Charges	Data Availability
Running	Yes	Yes	Available
Stopped	No	Yes	Available
Terminated	No	No	Not Recoverable

Ingress and Egress

Working in the cloud there are additional cost other then compute. * Ingress * Egress

Ingress cost tend to be minimal, however Egress cost can vary greatly depending on activity. Be careful when working in the cloud the cost you could accrue