AWS HealthOmics introduces resource fallback order for WDL workflows
AWS HealthOmics now allows users to define an ordered list of preferred accelerator types for tasks in WDL workflows, with an option to fallback to CPU instances when preferred accelerators are unavailable
Today, AWS HealthOmics introduced a resource fallback directive. This allows defining a list of preferred accelerator types for tasks in Workflow Description Language (WDL) workflows, automatically trying alternate options if the specified accelerator is unavailable, with the option to include CPU instances as the final fallback. Each accelerator profile can have a timeout set, choosing whether to expedite fallback ordering or increase the likelihood of securing the preferred accelerator. This feature is available in US East (N. Virginia, Ohio), US West (Oregon), Europe (Frankfurt, Ireland, London), Israel (Tel Aviv), and Asia Pacific (Seoul, Singapore, Tokyo) regions.
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 reduces the time spent diagnosing and resubmitting runs due to accelerator constraints, keeping production workflows running.