Skip to main content
Version: 25.3

Add a Studio

Select the Studios tab, and then select Add Studio. The options available are:

Compute environment requirements​

For AWS Batch compute environments:

  • CPUs allocated: The default allocation is 2 CPUs.
  • GPUs allocated: Available only if the selected compute environment has GPU support enabled. For more information about GPUs on AWS, see Amazon ECS task definitions for GPU workloads. The default allocation is 0 GPUs.
  • Maximum memory allocated: The default allocation is 8192 MiB of memory.
note

In AWS Batch, Seqera creates two job queues and their respective compute environments: a head queue that runs the parent Nextflow process on a single On-Demand instance, and a worker queue that executes per-task processes dispatched by the head node, typically on Spot instances. Studios uses only the head queue and its compute environment. The worker queue is not used.

For more information on AWS Batch configuration, see AWS Batch.

Single virtual machine compute environments are supported for AWS, Azure, and Google Cloud.

EFS file systems​

If you configured your compute environment to include an EFS file system with EFS file system > EFS mount path, the mount path must be explicitly specified. The mount path cannot be the same as your compute environment work directory. If the EFS file system is mounted as your compute environment work directory, snapshots cannot be saved and sessions fail.

To mount an EFS volume in a Studio session (for example, if your organization has a custom, managed, and standardized software stack in an EFS volume), add the EFS volume to the compute environment (system ID and mount path). The volume will be available at the specified mount path in the session.

SSH connection (public preview)​

From Enterprise v25.3.3, direct SSH connections to running Studios are available using standard SSH clients, VS Code Remote SSH, or terminal access. To use this feature:

  1. Enable SSH access for your workspace by setting the TOWER_DATA_STUDIO_SSH_ALLOWED_WORKSPACES environment variable during deployment. See Studios SSH configuration for configuration details.
  2. Add your SSH public key to your Seqera Platform user profile.
  3. Enable the SSH Connection toggle when adding a Studio.

For connection instructions and VS Code setup, see Connect to a Studio via SSH.

On this Page