# Service quotas and endpoints for AWS HealthOmics
<a name="healthomics-quotas"></a>

To connect programmatically to an AWS service, you use an endpoint. AWS services offer the following endpoint types in some or all of the AWS Regions that the service supports: IPv4 endpoints, dual-stack endpoints, and FIPS endpoints. Some services provide global endpoints. For more information, see [AWS service endpoints](rande.md).

Service quotas, also referred to as limits, are the maximum number of service resources or operations for your AWS account. For more information, see [AWS service quotas](aws_service_limits.md).

The following are the service endpoints and service quotas for this service.

## Service endpoints
<a name="endpoints"></a>

HealthOmics provides separate API endpoints for the storage, analytics, and workflow services. The [API quotas](https://docs.aws.amazon.com/omics/latest/dev/api-quotas.html) section in the *HealthOmics User Guide* provides the list of API operations for each service. The API endpoints use the following service codes:


| Service | Service code | 
| --- | --- | 
| HealthOmics Workflows | workflows | 
| HealthOmics Storage | storage | 
| HealthOmics Analytics | analytics | 

The resulting API endpoints have the following structure:

```
workflows-omics.region.amazonaws.com
storage-omics.region.amazonaws.com
analytics-omics.region.amazonaws.com
```

For regions that support FIPS API endpoints, the FIPS endpoints have the following structure:

```
workflows-omics-fips.region.amazonaws.com
storage-omics-fips.region.amazonaws.com
analytics-omics-fips.region.amazonaws.com
```

The following table lists the API endpoints for Regions where the HealthOmics service is available.


| Region Name | Region | Endpoint | Protocol | 
| --- | --- | --- | --- | 
| US East (N. Virginia)  | us-east-1 |  **Workflows:** workflows-omics.us-east-1.amazonaws.com **Storage:** storage-omics.us-east-1.amazonaws.com **Analytics:** analytics-omics.us-east-1.amazonaws.com **FIPS** **Workflows:** workflows-omics-fips.us-east-1.amazonaws.com **Storage:** storage-omics-fips.us-east-1.amazonaws.com **Analytics:** analytics-omics-fips.us-east-1.amazonaws.com  | HTTPS | 
| US West (Oregon)  | us-west-2  |  **Workflows:** workflows-omics.us-west-2.amazonaws.com **Storage:** storage-omics.us-west-2.amazonaws.com **Analytics:** analytics-omics.us-west-2.amazonaws.com **FIPS** **Workflows:** workflows-omics-fips.us-west-2.amazonaws.com **Storage:** storage-omics-fips.us-west-2.amazonaws.com **Analytics:** analytics-omics-fips.us-west-2.amazonaws.com  | HTTPS | 
| Asia Pacific (Singapore)  | ap-southeast-1 |  **Workflows:** workflows-omics.ap-southeast-1.amazonaws.com **Storage:** storage-omics.ap-southeast-1.amazonaws.com **Analytics:** analytics-omics.ap-southeast-1.amazonaws.com  | HTTPS | 
| Asia Pacific (Seoul)  | ap-northeast-2 |  **Workflows:** workflows-omics.ap-northeast-2.amazonaws.com **Storage:** storage-omics.ap-northeast-2.amazonaws.com **Analytics:** analytics-omics.ap-northeast-2.amazonaws.com  | HTTPS | 
| Europe (Frankfurt)  | eu-central-1 |  **Workflows:** workflows-omics.eu-central-1.amazonaws.com **Storage:** storage-omics.eu-central-1.amazonaws.com **Analytics:** analytics-omics.eu-central-1.amazonaws.com  | HTTPS | 
| Europe (Ireland)  | eu-west-1  |  **Workflows:** workflows-omics.eu-west-1.amazonaws.com **Storage:** storage-omics.eu-west-1.amazonaws.com **Analytics:** analytics-omics.eu-west-1.amazonaws.com  | HTTPS | 
| Europe (London) | eu-west-2  |  **Workflows:** workflows-omics.eu-west-2.amazonaws.com **Storage:** storage-omics.eu-west-2.amazonaws.com **Analytics:** analytics-omics.eu-west-2.amazonaws.com  | HTTPS | 
| Israel (Tel Aviv)  | il-central-1 |  **Workflows:** workflows-omics.il-central-1.amazonaws.com **Storage:** storage-omics.il-central-1.amazonaws.com **Analytics:** analytics-omics.il-central-1.amazonaws.com  | HTTPS | 

## Quotas for AWS HealthOmics
<a name="throtting"></a>

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](https://console.aws.amazon.com/servicequotas/home). In the navigation pane, choose **AWS services** and select **HealthOmics**.

To request a quota increase, see [Requesting a Quota Increase](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html) in the *Service Quotas User Guide*. If the quota is not yet available in Service Quotas, use the [limit increase form](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase).

The table below shows the default values for each of the HealthOmics quotas.

[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/general/latest/gr/healthomics-quotas.html)

For information about API operation quotas, see [ Quotas](https://docs.aws.amazon.com/omics/latest/dev/quotas.html) in the *HealthOmics User Guide*.