HCLS Overview
Amorphic HCLS integrates AWS health and life sciences services so you can store, process, and analyze clinical and genomic data alongside other Amorphic datasets.
| Capability | Documentation |
|---|---|
| HealthLake (FHIR) | Health Lake |
| HealthImaging | HealthImaging |
| Omics Storage | Omics Storage |
| Omics Analytics | Omics Analytics |
| Omics Workflows | Omics Workflows |
HCLS must be enabled in the environment before you can create or use these resources.
VPC Endpoints for HCLS
In external / private deployments, Amorphic provisions interface VPC endpoints for HCLS AWS services so VPC-hosted Lambdas can call HealthLake, HealthOmics, and HealthImaging APIs over PrivateLink without using the public internet. Private DNS is enabled on these endpoints, so existing application calls continue to use the standard regional service hostnames.
| Endpoint group | Created when | Services |
|---|---|---|
| HealthLake | External deployment and HCLS enabled | healthlake |
| HealthOmics | External deployment and HCLS enabled, in regions that support Omics PrivateLink (currently us-east-1 and us-west-2) | Control storage, workflows, and tags Omics APIs |
| HealthImaging | Same region conditions as Omics | Medical Imaging control plane and runtime |
- HCLS VPC endpoints are not created when HCLS is disabled, even if external deployment is enabled.
- Amazon S3 Tables has a separate interface VPC endpoint; see S3 Tables Datasets.
- AWS does not publish FIPS PrivateLink service names for HealthLake or HealthImaging. Omics FIPS PrivateLink names may be used in customer-managed VPC templates where AWS supports them.
For customer-managed VPC deployments, operators must deploy the matching HCLS interface endpoints in their VPC (typically attached to the Lambda security group) so private HCLS workloads can reach these services.