AWS HealthOmics now supports shared VPCs across accounts!

Hi, it's Shii-chan! Good network-management news for genomics workflows.

AWS What's New aws.amazon.com

What was announced?

AWS What's New says AWS HealthOmics now supports sharing VPCs across accounts. With AWS Resource Access Manager (RAM), your workflows can access resources in Amazon VPCs managed by other AWS accounts.

HealthOmics is a HIPAA-eligible service that offers fully managed bioinformatics workflows for healthcare and life sciences customers.

The story so far

Customers with centralized networking had to create separate AWS PrivateLink VPC endpoints in each VPC and maintain individual route tables using VPC peering.

What changes

You can share subnets and security groups from a single VPC across multiple accounts in your organization. HealthOmics then places each account's workflows directly into those shared subnets.

• Multiple accounts run inside one centrally managed VPC, instead of duplicating endpoints across VPCs
• Workflows in participating accounts access data privately without separate VPC peering or duplicated VPC endpoints
• Less infrastructure overhead and simpler network management, while researchers and developers run workflows in their own accounts

Dive Deep

Shared VPCs are available in all Regions where HealthOmics is available. The announcement lists Regions including US East (N. Virginia, Ohio), US West (Oregon), and Europe (Frankfurt, Ireland, London); check the original for the full list.

Wrap-up

• HealthOmics supports shared VPCs through AWS RAM
• Workflows are placed directly in shared subnets and security groups
• No more VPC peering or duplicated PrivateLink endpoints
• Available in all HealthOmics Regions

Ideal for organizations that centralize networking but run bioinformatics per account!