Service quotas and endpoints for AWS HealthOmics
Regions and endpoints for AWS HealthOmics
The following table lists the API endpoints for Regions where the HealthOmics service is available. For each Region, HealthOmics provides separate API endpoints for storage API operations, analytics API operations, and workflow API operations. The Quotas chapter in the HealthOmics User Guide provides the list of API operations for storage, analytics, and workflows.
The API endpoints have the following structure:
storage-omics.region.amazonaws.com analytics-omics.region.amazonaws.com workflows-omics.region.amazonaws.com Examples: storage-omics.us-east-1.amazonaws.com analytics-omics.eu-west-1.amazonaws.com workflows-omics.ap-southeast-1.amazonaws.com
| Region Name | Region | Endpoint | Protocol |
|---|---|---|---|
| US East (N. Virginia) | us-east-1 |
omics.us-east-1.amazonaws.com omics-fips.us-east-1.amazonaws.com |
HTTPS HTTPS |
| US West (Oregon) | us-west-2 |
omics.us-west-2.amazonaws.com omics-fips.us-west-2.amazonaws.com |
HTTPS HTTPS |
| Asia Pacific (Singapore) | ap-southeast-1 | omics.ap-southeast-1.amazonaws.com | HTTPS |
| Europe (Frankfurt) | eu-central-1 | omics.eu-central-1.amazonaws.com | HTTPS |
| Europe (Ireland) | eu-west-1 | omics.eu-west-1.amazonaws.com | HTTPS |
| Europe (London) | eu-west-2 | omics.eu-west-2.amazonaws.com | HTTPS |
| Israel (Tel Aviv) | il-central-1 | omics.il-central-1.amazonaws.com | HTTPS |
Quotas for AWS HealthOmics
Your AWS account initially contains the HealthOmics service default quotas in each Region. You can request increases for some quotas, and other quotas cannot be increased.
To view the quotas, open the Service Quotas console
To request a quota increase, see Requesting a Quota Increase in the Service Quotas User Guide.
If the quota is not yet available in Service Quotas, use the limit increase form
The table below shows the default values for each of the HealthOmics quotas.
| Name | Default | Adjustable | Description |
|---|---|---|---|
| Analytics - Maximum annotation stores | Each supported Region: 10 |
Yes |
The maximum number of annotation stores in the current AWS region |
| Analytics - Maximum concurrent variant or annotation store import jobs | Each supported Region: 5 |
Yes |
The maximum number of concurrent import jobs in the current AWS region |
| Analytics - Maximum files per annotation store import job | Each supported Region: 1 | No | The maximum number of files per annotation import job in the current AWS region |
| Analytics - Maximum files per variant store import job | Each supported Region: 1,000 |
Yes |
The maximum number of files per variant import job in the current AWS region |
| Analytics - Maximum shares per annotation store | Each supported Region: 10 |
Yes |
The maximum number of shares per annotation store in the current AWS region |
| Analytics - Maximum shares per variant store | Each supported Region: 10 |
Yes |
The maximum number of shares per variant store in the current AWS region |
| Analytics - Maximum size of each file in a variant import job | Each supported Region: 20 Gigabytes |
Yes |
The maximum size of one file in a variant import job in the current AWS region |
| Analytics - Maximum size of each file in an annotation import job | Each supported Region: 20 Gigabytes |
Yes |
The maximum size of one file in an annotation import job in the current AWS region |
| Analytics - Maximum variant stores | Each supported Region: 10 |
Yes |
The maximum number of variant stores in the current AWS region |
| Analytics - Maximum versions per annotation store | Each supported Region: 10 |
Yes |
The maximum number of versions per annotation store in the current AWS region |
| Storage - Maximum S3 access resource policy size | Each supported Region: 15 Kilobytes | No | The maximum size of the S3 access resource policy in the current AWS region |
| Storage - Maximum concurrent read set activation jobs | Each supported Region: 25 |
Yes |
The maximum number of concurrent read set activation jobs in the current AWS region |
| Storage - Maximum concurrent sequence and reference store export jobs | Each supported Region: 5 |
Yes |
The maximum number of concurrent export jobs from a sequence or reference store in the current AWS region |
| Storage - Maximum concurrent sequence or reference store import jobs | Each supported Region: 5 |
Yes |
The maximum number of concurrent import jobs for a sequence or reference store in the current AWS region |
| Storage - Maximum propagated set level tags | Each supported Region: 5 | No | The maximum number of set level tag keys, configured at the store level, that propagate to the S3 object in the current AWS region |
| Storage - Maximum read sets per activation job | Each supported Region: 20 |
Yes |
The maximum number of read sets per activation job in the current AWS region |
| Storage - Maximum read sets per export job | Each supported Region: 100 |
Yes |
The maximum number of read sets per export job in the current AWS region |
| Storage - Maximum read sets per import job | Each supported Region: 100 |
Yes |
The maximum number of read sets per import job in the current AWS region |
| Storage - Maximum read sets per sequence store | Each supported Region: 1,000,000 |
Yes |
The maximum number of read sets in a sequence store in the current AWS region |
| Storage - Maximum reference stores | Each supported Region: 1 | No | The maximum number of reference stores in the current AWS region |
| Storage - Maximum references per reference store | Each supported Region: 50 |
Yes |
The maximum number of references in a reference store in the current AWS region |
| Storage - Maximum sequence stores | Each supported Region: 20 |
Yes |
The maximum number of sequence stores in the current AWS region |
| Workflows - Maximum active GPUs | Each supported Region: 12 |
Yes |
The maximum number of concurrent active GPUs in the current AWS region |
| Workflows - Maximum active vCPUs |
us-east-1: 100,000 us-west-2: 100,000 Each of the other supported Regions: 3,000 |
Yes |
The maximum number of concurrent active vCPUs in the current AWS region |
| Workflows - Maximum concurrent active runs | Each supported Region: 10 |
Yes |
The maximum number of active runs in the current AWS region |
| Workflows - Maximum concurrent tasks per run | Each supported Region: 25 |
Yes |
The maximum number of concurrent tasks in each run in the current AWS region |
| Workflows - Maximum run duration | Each supported Region: 604,800 Seconds |
Yes |
The maximum workflow run duration in the current AWS region |
| Workflows - Maximum run groups | Each supported Region: 1,000 |
Yes |
The maximum number of run groups in the current AWS region |
| Workflows - Maximum runs (active or inactive) | Each supported Region: 5,000 |
Yes |
The maximum number of runs (active or inactive) in the current AWS region |
| Workflows - Maximum shares per workflow | Each supported Region: 100 |
Yes |
The maximum number of shares per workflow in the current AWS region |
| Workflows - Maximum static run storage capacity per run | Each supported Region: 9,600 |
Yes |
The maximum static run storage capacity in gibibytes (GiB) for each run in the current AWS region |
| Workflows - Maximum workflows | Each supported Region: 1,000 |
Yes |
The maximum number of workflows in the current AWS region |
For information about API operation quotas, see Quotas in the HealthOmics User Guide.
