AWS HealthOmics now supports third-party container registries for private workflows

AWS HealthOmics introduces support for third-party container registries, enabled through Amazon Elastic Container Registry (ECR) pull-through cache, along with URI remapping rules for automatic translation of third-party container URIs to ECR URIs. This enhancement enables AWS HealthOmics customers to more easily access containerized tools from popular third-party registries without needing to manually migrate them to private ECR repositories, or make changes to the workflow definition. AWS HealthOmics is a HIPAA-eligible service that helps healthcare and life sciences customers accelerate scientific breakthroughs with fully managed biological data stores and workflows.

The ECR pull-through cache capability allows bioinformatics teams to automatically retrieve and cache containers from popular registries including Amazon ECR Public, Docker Hub, Quay, GitHub Container Registry, GitLab Container Registry, Kubernetes container image registry, and Microsoft Azure Container Registry. This helps customers accelerate workflow development and execution by eliminating manual container synchronization tasks. Additionally, the new container URI remapping feature automatically translates third-party registry references in workflow definitions to corresponding private ECR URIs using customer-defined mapping rules, eliminating the need to manually update workflow definitions when migrating workflows.

ECR pull-through cache and container URI remapping features are now supported in all regions where AWS HealthOmics is available: US East (N. Virginia), US West (Oregon), Europe (Frankfurt, Ireland, London), Asia Pacific (Singapore), and Israel (Tel Aviv).

To learn more about these new features and how to implement them in your workflows, see the AWS HealthOmics documentation.

Categories: marketing:marchitecture/artificial-intelligence,general:products/aws-health

Source: Amazon Web Services

Latest Posts