AWS HealthOmics now supports shared VPCs

AWS HealthOmics supports shared VPC using AWS resource access manager (RAM) to access Amazon VPC resources managed in other AWS accounts, allowing customers to centralize network management by sharing subnets and security groups across multiple accounts from a single VPC. It deploys each account's workflows directly into these shared subnets, enabling multiple accounts to run within one centrally managed VPC without replicating endpoints per VPC. Participating accounts can privately access data without separate VPC peering connections or duplicated VPC endpoints. Previously, customers with centralized networks needed to create individual AWS PrivateLink VPC endpoints in each VPC and maintain separate route tables using VPC peering. Cross-account VPC sharing reduces infrastructure overhead and simplifies network management for organizations with centralized networks, while allowing researchers and developers to run bioinformatics workflows in their own accounts. The shared VPC is available in all regions where AWS HealthOmics is offered: US East (N. Virginia, Ohio), US West (Oregon), Europe (Frankfurt, Ireland, London), Israel (Tel Aviv), Asia Pacific (Singapore, Seoul, Tokyo).

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 is particularly useful for organizations that need to centralize network management and reduce infrastructure overhead across multiple accounts.