Amazon Translate endpoints and quotas
This section lists the the service endpoints and service quotas for the service. To connect programmatically to an AWS service, you use an endpoint. For more information, see AWS service endpoints.
In addition to the standard AWS endpoints, some AWS services offer the following endpoints in some or all of the AWS Regions that the service is supported in:
IPv4 endpoints — These endpoints support only IPv4 requests and have the following format:
service-name.region.amazonaws.com.rproxy.goskope.comDual-stack endpoints — These endpoints support both IPv4 requests and IPv6 requests and have the following format:
service-name.region.api.awsFIPS endpoints — These endpoints comply with the Federal Information Processing Standards (FIPS) and can support either IPv4 requests or dual-stack (IPv4 and IPv6) requests. FIPS endpoints have the following format:
service-name-fips.region.ip-endpoint-typeip-endpoint-typeisamazonaws.com(for IPv4 requests) orapi.aws(for IPv4 or IPv6 requests).
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.
Note
AWS recommends that you use Regional STS endpoints within your applications, and avoid using global (legacy) STS endpoints. Regional STS endpoints reduce latency, build in redundancy, and increase session token validity. For more information about configuring your applications to use a Regional STS endpoint, see AWS STS Regionalized endpoints in the AWS SDKs and Tools Reference Guide. For more information about global (legacy) AWS STS endpoints, including how to monitor for use of this type of endpoint, see How to use Regional AWS STS endpoints in the AWS Security blog.
Service endpoints
| Region Name | Region | Endpoint | Protocol |
|---|---|---|---|
| US East (Ohio) | us-east-2 |
translate.us-east-2.amazonaws.com translate-fips.us-east-2.amazonaws.com |
HTTPS HTTPS |
| US East (N. Virginia) | us-east-1 |
translate.us-east-1.amazonaws.com translate-fips.us-east-1.amazonaws.com |
HTTPS HTTPS |
| US West (N. California) | us-west-1 |
translate.us-west-1.amazonaws.com translate-fips.us-west-1.amazonaws.com |
HTTPS HTTPS |
| US West (Oregon) | us-west-2 |
translate.us-west-2.amazonaws.com translate-fips.us-west-2.amazonaws.com |
HTTPS HTTPS |
| Asia Pacific (Hong Kong) | ap-east-1 | translate.ap-east-1.amazonaws.com | HTTPS |
| Asia Pacific (Mumbai) | ap-south-1 | translate.ap-south-1.amazonaws.com | HTTPS |
| Asia Pacific (Seoul) | ap-northeast-2 | translate.ap-northeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Singapore) | ap-southeast-1 | translate.ap-southeast-1.amazonaws.com | HTTPS |
| Asia Pacific (Sydney) | ap-southeast-2 | translate.ap-southeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Tokyo) | ap-northeast-1 | translate.ap-northeast-1.amazonaws.com | HTTPS |
| Canada (Central) | ca-central-1 | translate.ca-central-1.amazonaws.com | HTTPS |
| Europe (Frankfurt) | eu-central-1 | translate.eu-central-1.amazonaws.com | HTTPS |
| Europe (Ireland) | eu-west-1 | translate.eu-west-1.amazonaws.com | HTTPS |
| Europe (London) | eu-west-2 | translate.eu-west-2.amazonaws.com | HTTPS |
| Europe (Paris) | eu-west-3 | translate.eu-west-3.amazonaws.com | HTTPS |
| Europe (Stockholm) | eu-north-1 | translate.eu-north-1.amazonaws.com | HTTPS |
| AWS GovCloud (US-West) | us-gov-west-1 |
translate.us-gov-west-1.amazonaws.com translate-fips.us-gov-west-1.amazonaws.com |
HTTPS HTTPS |
Service quotas
| Name | Default | Adjustable | Description |
|---|---|---|---|
| Concurrent batch translation jobs | Each supported Region: 10 |
Yes |
The maximum number of concurrent batch translation jobs in this account in the current Region. |
| Custom terminology files | Each supported Region: 100 |
Yes |
The maximum number of custom terminology files you can store in this account in the current Region. |
| Parallel data resources | Each supported Region: 1,000 |
Yes |
The maximum number of parallel data resources in this account in the current Region. |
For more information, see Guidelines and Quotas in the Amazon Translate Developer Guide.
