AWS HealthOmics introduces resource fallback order for Nextflow workflows
AWS HealthOmics introduces a resource fallback directive for Nextflow workflows, allowing researchers and bioinformaticians to define an ordered list of preferred accelerator types and reduce time spent diagnosing and resubmitting runs due to accelerator constraints
AWS HealthOmics now supports resource fallback directives for Nextflow workflow tasks, allowing researchers to define a prioritized list of accelerator types with an optional CPU instance fallback. This reduces diagnosis and resubmission time due to accelerator constraints, keeping production workflows running. AWS HealthOmics is a HIPAA-compliant service that accelerates scientific breakthroughs at scale for healthcare and life sciences customers with fully managed bioinformatics workflows. The resource fallback enables priority acceleration, automatically moving to specified alternatives without resubmission if the preferred accelerator is unavailable. Each accelerator profile has a configurable timeout, controlling search duration, where shorter timeouts speed fallback progression and longer timeouts increase the chance of securing the preferred accelerator. Including a CPU profile as the final fallback can also improve the likelihood of instance allocation. This feature is available in all AWS HealthOmics regions, including US East, US West, Europe, Israel, and Asia Pacific. For more information, see the detailed documentation on advanced resource configuration and Nextflow.
Why it matters
AWS HealthOmics is a HIPAA-eligible service that helps healthcare and life sciences customers accelerate scientific breakthroughs at scale with fully managed bioinformatics workflows. This update allows researchers and bioinformaticians to reduce time spent diagnosing and resubmitting runs due to accelerator constraints and keep production workflows running.