AWS Database Migration Service 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 |
dms.us-east-2.amazonaws.com dms-fips.us-east-2.amazonaws.com |
HTTPS HTTPS |
| US East (N. Virginia) | us-east-1 |
dms.us-east-1.amazonaws.com dms-fips.us-east-1.amazonaws.com |
HTTPS HTTPS |
| US West (N. California) | us-west-1 |
dms.us-west-1.amazonaws.com dms-fips.us-west-1.amazonaws.com |
HTTPS HTTPS |
| US West (Oregon) | us-west-2 |
dms.us-west-2.amazonaws.com dms-fips.us-west-2.amazonaws.com |
HTTPS HTTPS |
| Africa (Cape Town) | af-south-1 | dms.af-south-1.amazonaws.com | HTTPS |
| Asia Pacific (Hong Kong) | ap-east-1 | dms.ap-east-1.amazonaws.com | HTTPS |
| Asia Pacific (Hyderabad) | ap-south-2 | dms.ap-south-2.amazonaws.com | HTTPS |
| Asia Pacific (Jakarta) | ap-southeast-3 | dms.ap-southeast-3.amazonaws.com | HTTPS |
| Asia Pacific (Malaysia) | ap-southeast-5 | dms.ap-southeast-5.amazonaws.com | HTTPS |
| Asia Pacific (Melbourne) | ap-southeast-4 | dms.ap-southeast-4.amazonaws.com | HTTPS |
| Asia Pacific (Mumbai) | ap-south-1 | dms.ap-south-1.amazonaws.com | HTTPS |
| Asia Pacific (Osaka) | ap-northeast-3 | dms.ap-northeast-3.amazonaws.com | HTTPS |
| Asia Pacific (Seoul) | ap-northeast-2 | dms.ap-northeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Singapore) | ap-southeast-1 | dms.ap-southeast-1.amazonaws.com | HTTPS |
| Asia Pacific (Sydney) | ap-southeast-2 | dms.ap-southeast-2.amazonaws.com | HTTPS |
| Asia Pacific (Thailand) | ap-southeast-7 | dms.ap-southeast-7.amazonaws.com | HTTPS |
| Asia Pacific (Tokyo) | ap-northeast-1 | dms.ap-northeast-1.amazonaws.com | HTTPS |
| Canada (Central) | ca-central-1 | dms.ca-central-1.amazonaws.com | HTTPS |
| Canada West (Calgary) | ca-west-1 | dms.ca-west-1.amazonaws.com | HTTPS |
| Europe (Frankfurt) | eu-central-1 | dms.eu-central-1.amazonaws.com | HTTPS |
| Europe (Ireland) | eu-west-1 | dms.eu-west-1.amazonaws.com | HTTPS |
| Europe (London) | eu-west-2 | dms.eu-west-2.amazonaws.com | HTTPS |
| Europe (Milan) | eu-south-1 | dms.eu-south-1.amazonaws.com | HTTPS |
| Europe (Paris) | eu-west-3 | dms.eu-west-3.amazonaws.com | HTTPS |
| Europe (Spain) | eu-south-2 | dms.eu-south-2.amazonaws.com | HTTPS |
| Europe (Stockholm) | eu-north-1 | dms.eu-north-1.amazonaws.com | HTTPS |
| Europe (Zurich) | eu-central-2 | dms.eu-central-2.amazonaws.com | HTTPS |
| Israel (Tel Aviv) | il-central-1 | dms.il-central-1.amazonaws.com | HTTPS |
| Mexico (Central) | mx-central-1 | dms.mx-central-1.amazonaws.com | HTTPS |
| Middle East (Bahrain) | me-south-1 | dms.me-south-1.amazonaws.com | HTTPS |
| Middle East (UAE) | me-central-1 | dms.me-central-1.amazonaws.com | HTTPS |
| South America (São Paulo) | sa-east-1 | dms.sa-east-1.amazonaws.com | HTTPS |
| AWS GovCloud (US-East) | us-gov-east-1 | dms.us-gov-east-1.amazonaws.com | HTTPS |
| AWS GovCloud (US-West) | us-gov-west-1 | dms.us-gov-west-1.amazonaws.com | HTTPS |
Service quotas
| Name | Default | Adjustable | Description |
|---|---|---|---|
| Certificate count | Each supported Region: 100 |
Yes |
The maximum number of certificates allowed in this account in the current Region. |
| Endpoint count | Each supported Region: 1,000 |
Yes |
The maximum number of endpoints allowed in this account in the current Region. |
| Endpoints per instance | Each supported Region: 100 |
Yes |
The maximum number of endpoints allowed per replication instance. |
| Event subscriptions | Each supported Region: 60 |
Yes |
The maximum number of AWS DMS events that you can subscribe to. |
| Number of DMS Fleet Advisor collector instances | Each supported Region: 10 | No | Maximum number of created instances of DMS Fleet Advisor collector |
| Number of Data Migrations | Each supported Region: 1,000 |
Yes |
Maximum number of data migrations |
| Number of Data Migrations per Migration Project | Each supported Region: 10 | No | Maximum number of data migrations allowed per migration project |
| Number of Data Providers | Each supported Region: 1,000 |
Yes |
Maximum number of data providers |
| Number of Instance Profiles | Each supported Region: 60 |
Yes |
Maximum number of instance profiles |
| Number of Migration Projects | Each supported Region: 10 |
Yes |
Maximum number of migration projects |
| Number of data files DMS Fleet Advisor can send per hour | Each supported Region: 500 per hour | No | Maximum number of files that DMS Fleet Advisor collector can send per hour |
| Number of database objects DMS Fleet Advisor can process | Each supported Region: 50,000,000 | No | The total number of database objects that AWS DMS Fleet Advisor can process. A database object is any data structure used to store or reference data, including tables, views, stored procedures, functions, and triggers |
| Number of monitored objects in DMS Fleet Advisor collector | Each supported Region: 2,000 | No | Maximum number of monitored objects that a customer can add in a single DMS Fleet Advisor collector |
| Number of running Data Migrations | Each supported Region: 500 |
Yes |
Maximum number of running data migrations simultaneously. |
| Replication instances | Each supported Region: 60 |
Yes |
The maximum number of replication instances allowed in this account in the current Region. |
| Serverless replications | Each supported Region: 100 |
Yes |
The maximum number of serverless replications allowed in this account in the current Region. |
| Subnet groups | Each supported Region: 60 |
Yes |
The maximum number of subnet groups allowed in this account in the current Region. |
| Subnets per subnet group | Each supported Region: 60 |
Yes |
The maximum number of subnets allowed per subnet group. |
| Task count | Each supported Region: 600 |
Yes |
The maximum number of tasks allowed in this account in the current Region. |
| The amount of collected data in DMS Fleet Advisor | Each supported Region: 10 Gigabytes | No | The amount of data that can be collected by all DMS Fleet Advisor collectors |
| Total storage | Each supported Region: 30,000 Gigabytes |
Yes |
The maximum total storage (in GB) for all replication instances added together. |
