AWS HealthOmics introduces resource fallback order for WDL workflows
AWS HealthOmics now allows researchers to set fallback orders for accelerator types in WDL workflows, reducing delays from resource constraints and improving workflow continuity.
AWS HealthOmics has introduced a resource fallback directive for Workflow Description Language (WDL) workflows, enabling users to specify an ordered list of preferred accelerator types. This feature allows tasks to automatically switch to alternative accelerators or CPU instances when preferred options are unavailable, eliminating the need for manual resubmission. The directive is designed to minimize downtime in production workflows by streamlining resource allocation processes. Researchers and bioinformaticians can now prioritize accelerators based on availability without interrupting workflow execution.
The fallback mechanism includes configurable timeouts for each accelerator profile, giving users control over how long HealthOmics searches for a preferred resource before moving to the next option. Shorter timeouts expedite the fallback process, while longer timeouts increase the likelihood of securing the preferred accelerator. This flexibility helps balance speed and resource reservation efficiency. Users can also designate CPU instances as a final fallback to ensure task completion even when specialized accelerators are constrained.
AWS HealthOmics is a HIPAA-eligible service that supports healthcare and life sciences customers in accelerating scientific research through managed bioinformatics workflows. The new resource fallback feature enhances the service’s ability to handle large-scale workflows by reducing interruptions caused by resource limitations. By automating the fallback process, the service improves operational efficiency for teams running critical bioinformatics tasks.
The resource fallback directive is now available in all AWS HealthOmics Regions, including US East (N. Virginia, Ohio), US West (Oregon), Europe (Frankfurt, Ireland, London), Israel (Tel Aviv), and Asia Pacific (Seoul, Singapore, Tokyo). Users can implement this feature immediately to optimize their WDL workflows. For detailed guidance, AWS provides documentation on advanced resource configuration to help users customize their fallback strategies.