Seqera Compute

Seqera Compute enables you to run pipelines and Studio sessions in Seqera Cloud in a fully managed and optimized AWS environment. Seqera automatically provisions and manages all the underlying resources, including AWS accounts, credentials, roles, compute environments, and S3 storage buckets, requiring minimal user configuration. Using prepaid credits enables control and visibility of the compute spend in each of your organization's workspaces.

Manage Seqera Compute credits

Seqera Compute uses prepaid credits with real-time billing. Credits are deducted as tasks complete. See Billing and credit management for details.

Default limits

Compute environment limits

Seqera Compute environments automatically provision cloud resources when you launch pipelines or Studios. The maximum resources that can be allocated to a Seqera Compute environment are:

• 48 vCPUs
• 192 GiB memory

Running workflows that request resources exceeding these limits will result in errors.

Workspace limits

Seqera Compute has default workspace limits on compute environments, and organization limits on data storage and CPU cores.

	Basic	Pro
Cloud storage	25 GB	Unlimited
Compute environments per workspace	5	20
Total CPU cores	100	1000

info

Contact us to discuss custom limits for Pro, academic, or evaluation licenses.

Create a Seqera Compute environment

1. In a workspace with Seqera Compute enabled, select Compute environments > New environment.

2. Enter a descriptive name for this environment, such as Seqera Compute 1 (eu-west-1).

3. Under Platform, select Seqera Compute.

4. Select a target execution Region.

   info

   Seqera Compute is available in the following AWS regions:

   Americas	Europe	Asia Pacific	Middle East & Africa
   us-east-1 (Northern Virginia, USA)	eu-central-1 (Frankfurt, Germany)	ap-east-1 (Hong Kong)	af-south-1 (Cape Town, South Africa)
   us-east-2 (Ohio, USA)	eu-north-1 (Stockholm, Sweden)	ap-northeast-1 (Tokyo, Japan)	me-south-1 (Bahrain)
   us-west-1 (Northern California, USA)	eu-south-1 (Milan, Italy)	ap-northeast-2 (Seoul, South Korea)
   us-west-2 (Oregon, USA)	eu-west-1 (Ireland)	ap-northeast-3 (Osaka, Japan)
   ca-central-1 (Central, Canada)	eu-west-2 (London, UK)	ap-south-1 (Mumbai, India)
   sa-east-1 (São Paulo, Brazil)	eu-west-3 (Paris, France)	ap-southeast-1 (Singapore)
   		ap-southeast-2 (Sydney, Australia)
   		ap-southeast-3 (Jakarta, Indonesia)

5. Configure any advanced options described in the next section, as needed.

6. Select Add to complete the Seqera Compute environment configuration and return to the compute environments list. It will take a few seconds for the compute environment resources to be created before you are ready to launch pipelines or add studios.

info

See Launch pipelines to start executing workflows in your Seqera Compute environment.

Advanced options (optional)

1. Toggle Automatic data retention policy. When enabled (default), intermediary files are deleted after 28 days to manage cloud storage usage and cost.

2. Enter a relative Work directory path to be appended to the S3 storage bucket Seqera creates for this compute environment.

3. Enter pre- or post-run Bash scripts that execute before or after the Nextflow pipeline execution in your environment.

4. Enter Global Nextflow configuration settings for all pipeline runs launched with this environment. Values defined here are pre-filled in the Nextflow config file field in the pipeline launch form. These values can be overridden at pipeline launch.

   info

   Configuration settings in this field override the same values in the pipeline repository nextflow.config file. See Nextflow config file for more information on configuration priority.

5. Under Environment variables, add each variable with a Name, Value, and Target Environment:

   • Head job: Adds the variable to the Nextflow head job container, which evaluates nextflow.config and submits tasks to the compute backend. Use this target for variables that Nextflow or its plugins read, such as NXF_OPTS, NXF_JVM_ARGS, NXF_PLUGINS_DEFAULT, or proxy settings the head node uses to reach external services.
   • Compute job: Adds the variable to the worker containers that run individual pipeline tasks. Use this target for variables your pipeline tools read, such as OPENAI_API_KEY for a process that calls the OpenAI API, registry credentials needed inside the task container, or tool-specific settings like JAVA_HOME.
   • Head and Compute jobs: Adds the variable to both the head job and the compute jobs. Use this target for values needed in both places, such as an HTTP proxy used by both Nextflow and task tools, or a credential needed in both the head job and individual compute tasks.
   note

   For sensitive values such as API keys and tokens, use pipeline secrets instead of custom environment variables. Custom environment variables are stored in the compute environment configuration and cannot be edited after creation. To rotate a value, recreate the compute environment.