# AWS DataSync endpoints and quotas
<a name="datasync"></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="datasync-region"></a>

**Topics**
+ [DataSync transfers](#datasync-transfer-region)

### DataSync transfers
<a name="datasync-transfer-region"></a>


| Region Name | Region | Endpoint | Protocol | 
| --- | --- | --- | --- | 
| US East (Ohio) | us-east-2 |  datasync.us-east-2.amazonaws.com <br /> datasync-fips.us-east-2.api.aws <br /> datasync.us-east-2.api.aws <br /> datasync-fips.us-east-2.amazonaws.com  | HTTPS<br />HTTPS<br />HTTPS<br />HTTPS | 
| US East (N. Virginia) | us-east-1 |  datasync.us-east-1.amazonaws.com <br /> datasync-fips.us-east-1.api.aws <br /> datasync-fips.us-east-1.amazonaws.com <br /> datasync.us-east-1.api.aws  | HTTPS<br />HTTPS<br />HTTPS<br />HTTPS | 
| US West (N. California) | us-west-1 |  datasync.us-west-1.amazonaws.com <br /> datasync.us-west-1.api.aws <br /> datasync-fips.us-west-1.api.aws <br /> datasync-fips.us-west-1.amazonaws.com  | HTTPS<br />HTTPS<br />HTTPS<br />HTTPS | 
| US West (Oregon) | us-west-2 |  datasync.us-west-2.amazonaws.com <br /> datasync-fips.us-west-2.api.aws <br /> datasync.us-west-2.api.aws <br /> datasync-fips.us-west-2.amazonaws.com  | HTTPS<br />HTTPS<br />HTTPS<br />HTTPS | 
| Africa (Cape Town) | af-south-1 |  datasync.af-south-1.amazonaws.com <br /> datasync.af-south-1.api.aws  | HTTPS<br />HTTPS | 
| Asia Pacific (Hong Kong) | ap-east-1 |  datasync.ap-east-1.amazonaws.com <br /> datasync.ap-east-1.api.aws  | HTTPS<br />HTTPS | 
| Asia Pacific (Hyderabad) | ap-south-2 |  datasync.ap-south-2.amazonaws.com <br /> datasync.ap-south-2.api.aws  | HTTPS<br />HTTPS | 
| Asia Pacific (Jakarta) | ap-southeast-3 |  datasync.ap-southeast-3.amazonaws.com <br /> datasync.ap-southeast-3.api.aws  | HTTPS<br />HTTPS | 
| Asia Pacific (Malaysia) | ap-southeast-5 |  datasync.ap-southeast-5.amazonaws.com <br /> datasync.ap-southeast-5.api.aws  | HTTPS<br />HTTPS | 
| Asia Pacific (Melbourne) | ap-southeast-4 |  datasync.ap-southeast-4.amazonaws.com <br /> datasync.ap-southeast-4.api.aws  | HTTPS<br />HTTPS | 
| Asia Pacific (Mumbai) | ap-south-1 |  datasync.ap-south-1.amazonaws.com <br /> datasync.ap-south-1.api.aws  | HTTPS<br />HTTPS | 
| Asia Pacific (New Zealand) | ap-southeast-6 |  datasync.ap-southeast-6.amazonaws.com <br /> datasync.ap-southeast-6.api.aws  | HTTPS<br />HTTPS | 
| Asia Pacific (Osaka) | ap-northeast-3 |  datasync.ap-northeast-3.amazonaws.com <br /> datasync.ap-northeast-3.api.aws  | HTTPS<br />HTTPS | 
| Asia Pacific (Seoul) | ap-northeast-2 |  datasync.ap-northeast-2.amazonaws.com <br /> datasync.ap-northeast-2.api.aws  | HTTPS<br />HTTPS | 
| Asia Pacific (Singapore) | ap-southeast-1 |  datasync.ap-southeast-1.amazonaws.com <br /> datasync.ap-southeast-1.api.aws  | HTTPS<br />HTTPS | 
| Asia Pacific (Sydney) | ap-southeast-2 |  datasync.ap-southeast-2.amazonaws.com <br /> datasync.ap-southeast-2.api.aws  | HTTPS<br />HTTPS | 
| Asia Pacific (Taipei) | ap-east-2 |  datasync.ap-east-2.amazonaws.com <br /> datasync.ap-east-2.api.aws  | HTTPS<br />HTTPS | 
| Asia Pacific (Thailand) | ap-southeast-7 |  datasync.ap-southeast-7.amazonaws.com <br /> datasync.ap-southeast-7.api.aws  | HTTPS<br />HTTPS | 
| Asia Pacific (Tokyo) | ap-northeast-1 |  datasync.ap-northeast-1.amazonaws.com <br /> datasync.ap-northeast-1.api.aws  | HTTPS<br />HTTPS | 
| Canada (Central) | ca-central-1 |  datasync.ca-central-1.amazonaws.com <br /> datasync.ca-central-1.api.aws <br /> datasync-fips.ca-central-1.amazonaws.com <br /> datasync-fips.ca-central-1.api.aws  | HTTPS<br />HTTPS<br />HTTPS<br />HTTPS | 
| Canada West (Calgary) | ca-west-1 |  datasync.ca-west-1.amazonaws.com <br /> datasync.ca-west-1.api.aws <br /> datasync-fips.ca-west-1.amazonaws.com <br /> datasync-fips.ca-west-1.api.aws  | HTTPS<br />HTTPS<br />HTTPS<br />HTTPS | 
| Europe (Frankfurt) | eu-central-1 |  datasync.eu-central-1.amazonaws.com <br /> datasync.eu-central-1.api.aws  | HTTPS<br />HTTPS | 
| Europe (Ireland) | eu-west-1 |  datasync.eu-west-1.amazonaws.com <br /> datasync.eu-west-1.api.aws  | HTTPS<br />HTTPS | 
| Europe (London) | eu-west-2 |  datasync.eu-west-2.amazonaws.com <br /> datasync.eu-west-2.api.aws  | HTTPS<br />HTTPS | 
| Europe (Milan) | eu-south-1 |  datasync.eu-south-1.amazonaws.com <br /> datasync.eu-south-1.api.aws  | HTTPS<br />HTTPS | 
| Europe (Paris) | eu-west-3 |  datasync.eu-west-3.amazonaws.com <br /> datasync.eu-west-3.api.aws  | HTTPS<br />HTTPS | 
| Europe (Spain) | eu-south-2 |  datasync.eu-south-2.amazonaws.com <br /> datasync.eu-south-2.api.aws  | HTTPS<br />HTTPS | 
| Europe (Stockholm) | eu-north-1 |  datasync.eu-north-1.amazonaws.com <br /> datasync.eu-north-1.api.aws  | HTTPS<br />HTTPS | 
| Europe (Zurich) | eu-central-2 |  datasync.eu-central-2.amazonaws.com <br /> datasync.eu-central-2.api.aws  | HTTPS<br />HTTPS | 
| Israel (Tel Aviv) | il-central-1 |  datasync.il-central-1.amazonaws.com <br /> datasync.il-central-1.api.aws  | HTTPS<br />HTTPS | 
| Mexico (Central) | mx-central-1 |  datasync.mx-central-1.amazonaws.com <br /> datasync.mx-central-1.api.aws  | HTTPS<br />HTTPS | 
| Middle East (Bahrain) | me-south-1 |  datasync.me-south-1.amazonaws.com <br /> datasync.me-south-1.api.aws  | HTTPS<br />HTTPS | 
| Middle East (UAE) | me-central-1 |  datasync.me-central-1.amazonaws.com <br /> datasync.me-central-1.api.aws  | HTTPS<br />HTTPS | 
| South America (São Paulo) | sa-east-1 |  datasync.sa-east-1.amazonaws.com <br /> datasync.sa-east-1.api.aws  | HTTPS<br />HTTPS | 
|  AWS GovCloud (US-East) | us-gov-east-1 |  datasync.us-gov-east-1.amazonaws.com <br /> datasync.us-gov-east-1.api.aws <br /> datasync-fips.us-gov-east-1.amazonaws.com <br /> datasync-fips.us-gov-east-1.api.aws  | HTTPS<br />HTTPS<br />HTTPS<br />HTTPS | 
|  AWS GovCloud (US-West) | us-gov-west-1 |  datasync.us-gov-west-1.amazonaws.com <br /> datasync-fips.us-gov-west-1.amazonaws.com <br /> datasync-fips.us-gov-west-1.api.aws <br /> datasync.us-gov-west-1.api.aws  | HTTPS<br />HTTPS<br />HTTPS<br />HTTPS | 

## Service quotas
<a name="datasync-quotas-gr"></a>

**Topics**
+ [DataSync task quotas](#datasync-task-quotas-gr)

### DataSync task quotas
<a name="datasync-task-quotas-gr"></a>

The following table describes the quotas for DataSync tasks in a specific AWS account and AWS Region.


| Resource | Quota | Adjustable | 
| --- | --- | --- | 
| Maximum number of tasks you can create | 100 | Yes | 
| **(Enhanced mode tasks)** Maximum number of source and destination objects that DataSync can work with per task execution<br />For more information, see [How DataSync transfers files, objects, and directories](https://docs.aws.amazon.com/datasync/latest/userguide/how-datasync-transfer-works.html#transferring-files) | Virtually unlimited | N/A | 
| **(Basic mode tasks)** Maximum number of source and destination files, objects, and directories that DataSync can work with per task execution between self-managed storage or other clouds and AWS services<br />For more information, see [How DataSync transfers files, objects, and directories](https://docs.aws.amazon.com/datasync/latest/userguide/how-datasync-transfer-works.html#transferring-files) | 50 million Remember the following about this quota:   If you transfer Amazon S3 objects with prefixes, the prefixes are treated as directories and count towards the quota. For example, DataSync would consider`s3://bucket/foo/bar.txt` as two directories (`./` and `./foo/`) and one object (`bar.txt`).   If your task is transferring more than 20 million files, objects, or directories, make sure that you allocate a minimum of 64 GB of RAM to your DataSync agent. For more information, see [agent requirements for transfers](https://docs.aws.amazon.com/datasync/latest/userguide/agent-requirements.html#agent-tranfer-resource-requirements).    | Yes Instead of requesting an increase, you can create tasks that focus on specific directories using include and exclude filters. For more information, see [Filtering the data transferred by AWS DataSync](https://docs.aws.amazon.com/datasync/latest/userguide/filtering.html).   | 
| **(Basic mode tasks)** Maximum number of source and destination files, objects, and directories that DataSync can work with per task execution between AWS storage services<br />For more information, see [How DataSync transfers files, objects, and directories](https://docs.aws.amazon.com/datasync/latest/userguide/how-datasync-transfer-works.html#transferring-files) | 25 million If you transfer Amazon S3 objects with prefixes, the prefixes are treated as directories and count towards the quota. For example, DataSync would consider`s3://bucket/foo/bar.txt` as two directories (`./` and `./foo/`) and one object (`bar.txt`).  | Yes Instead of requesting an increase, you can create tasks that focus on specific directories using include and exclude filters. For more information, see [Filtering the data transferred by AWS DataSync](https://docs.aws.amazon.com/datasync/latest/userguide/filtering.html).   | 
| Maximum throughput per task (for transfers that use a DataSync agent) | 10 Gbps | No | 
| Maximum throughput per task (for transfers that don't use a DataSync agent) | 5 Gbps | No | 
| Maximum number of characters you can include in a task filter | 102,400 characters If you're using the DataSync console, this limit includes all the characters combined in your include and exclude patterns.  | No | 
| Maximum number of queued executions for a single task | 50 | No | 
| Maximum number of concurrent Enhanced mode task executions | 120 | No | 
| Number of days a task execution's history is retained | 30 | No |