Cloud Workstation
Learn about the Cloud Workstation app, which lets you explore and manipulate data on the DNAnexus Platform, as you would on a local Linux machine.
Why Use Cloud Workstation
Cloud Workstation sets up a virtual workstation that lets you access and work with data stored on the DNAnexus Platform, just as you would on a local Linux machine, but without having to download files to your computer.
You can configure this workstation to use any of the wide range of powerful instance types available on the Platform. You can easily save files or analysis results from your workstation session, to the project within which you launched it. You can also create a snapshot of the session, if you want to pick up work at a later date.
Launching Cloud Workstation
Before You Begin
You'll need the dx command-line client to access the virtual workstation. Download and install it if you haven't already done so.
You'll also need to set up SSH if you haven't already done so.
Launching the App
From the command line, use the dx client to navigate to the project you'd like to work in.
Note that to run the Cloud Workstation app from within a project, you must have either CONTRIBUTE or ADMINISTER access to that project.
Next, use dx run to launch Cloud Workstation, taking care to add the --ssh flag:
Once the app launches, you'll see a list of optional parameters:
See the in-product app documentation for more on setting these parameters.
Once you've either set or skipped the optional parameters, you'll be connected to the worker running Cloud Workstation. You'll see the following in your terminal:
Preparing Your Workstation
To access a file within your virtual workstation, you must download it from a Platform project to the workstation. If you want to save a file from your workstation session, you must upload it to the workstation's parent project.
In order to do either, you must prepare your workstation by running the following two commands:
The first command unsets an environment variable that's set when the workstation is launched. This allows you to navigate from within the workstation to any of the projects to which you have access. The second command invokes dx cd to change your workstation's working directory, to that of the parent project.
For more information about these and other environment variables used within the execution environment, see this Execution Environment Reference.
Your virtual workstation is now ready to use.
Accessing Files
To access a file within your virtual workstation, you must download it to the workstation, using the dx download command.
This includes files stored in the workstation's parent project.
You can download any file from any project to which you have access.
To download a file named my-file.txt from the parent project, use the command:
To download a set of reads from the SRR100022 exome from the public Demo Data project:
When downloading a file or files from a project other than the parent project, you might want to avoid having to enter the project ID. To do this, start by getting a list of projects to which you have access. Then choose a project:
Now you can download a file to your virtual workstation, by entering only the filename:
Getting Additional Tools
Your virtual workstation has network access, so you can download and use any tool you need during your session, just as you would on a Linux workstation.
If you would like a tool or tools to be available within your workstation when it launches, you can customize the Cloud Workstation app to enable this.
Saving Files
If you want to save any files from your workstation session, you must upload these files to the workstation's parent project, using dx upload.
Note that if you changed project context as you downloaded files to your virtual workstation, you must use the --path flag with dx upload, to ensure you upload files to the correct project:
Use the following commands to perform a test upload:
You should see the contents of your project change, with the new file test_file_from_workstation.txt appearing in the file list, between the first and second invocations of dx ls.
Terminating the Session
By default, your virtual workstation will automatically shut down once the maximum session length is reached. If you want to shut it down earlier, use the dx terminate command, taking care to use $DX_JOB_ID to include the workstation's job ID:
You can also shut down the workstation by finding the job in the UI's Monitor page, and clicking the Terminate button at the right end of the row displaying info on the job.
The contents of your virtual workstation will be destroyed on termination. Before the end of your session, be sure to upload any files you want to save.
Execution Environment
Instance Type
By default, your virtual workstation will launch on a mem1_ssd1_v2_x8 instance type, which has 8 cores, 16 GB of memory, and 180 GB of storage. To run the app on a different instance type, use the --instance-type flag with dx run, as in:
See the Instance Types page for a full list of available instance types.
Operating System
The Cloud Workstation app is set up to use Ubuntu 24.04.
Job Execution Environment vs. Local Environment
When connecting to the execution environment, you are using the job's credentials to interact with the DNAnexus API. The job has a limited subset of your Platform user permissions. By default, a job running the Cloud Workstation app has VIEW permissions to all projects to which you have VIEW or greater permissions.
By default, the dx select command hides projects to which you have only VIEW permissions. To see a list of those projects, use the command dx select --level=VIEW.
Customizing Cloud Workstation
The Cloud Workstation app provides the minimum functionality necessary to support an interactive workstation.
To make your own version with enhanced functionality, you can create a custom applet, based on the Cloud Workstation app. To get the original source code for the the Cloud Workstation app, run dx get app-cloud_workstation. See Introduction to Building Apps to learn how to build a custom applet that incorporates an existing executable.
Possible customizations include:
Specifying different inputs
Prepackaging external utilities for use within the worker
Changing the instance type of the worker
Changing access permissions
Last updated
Was this helpful?