AWS HealthOmics variant stores and annotation stores will no longer be open to new customers starting November 7th, 2025. If you would like to use variant stores or annotation stores, sign up prior to that date. Existing customers can continue to use the service as normal. For more information, see AWS HealthOmics variant store and annotation store availability change.
Private workflows in HealthOmics
Use Private workflows when you want to create your own workflow definition. The workflow definition specifies information about the workflow and defines the workflow tasks. A run is a single invocation of a workflow, and a task is a single process within the run.
HealthOmics supports workflow definitions that you create in Workflow Description Language (WDL), Common Workflow Language (CWL), or Nextflow.
HealthOmics workflows provide the following optional features:
-
Run groups – You can add private workflows to a run group to control compute usage. A run group is a collection of workflow runs that share a set of resource limits, such as maximum concurrent runs and maximum run duration. You set these limits to control the compute resources that the run group consumes.
-
Call caching – You can use a call cache to save and reuse task outputs, which results in shorter run durations and compute cost savings.
-
Sharing workflows – You can share your private workflows with other AWS accounts in the same Region.
-
Workflow versions – You can create versions of a private workflow. Workflow versioning provides the ability for users to choose when to start using updated functionality. Workflow versions are immutable and provide the same level of data provenance as workflows.
For information about configuring IAM permissions for workflows, see IAM permissions for HealthOmics.
For full examples of how to use HealthOmics private workflows, see
HealthOmics Github tutorials
Topics
