Deploying your Amazon DataSync agent in an Amazon Web Services Region - Amazon DataSync
Transferring data from a cloud file system to another cloud file system or Amazon S3Transferring data from Amazon S3 to Amazon file systems
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Deploying your Amazon DataSync agent in an Amazon Web Services Region

The following guidance can help with common scenarios if you deploy an Amazon DataSync agent in an Amazon Web Services Region. If you don't have an agent yet, see Deploy your agent on Amazon EC2.

Transferring data from a cloud file system to another cloud file system or Amazon S3

To transfer data between Amazon Web Services accounts, or from a cloud file system, the DataSync agent must be located in the same Amazon Web Services Region and Amazon Web Services account where the source file system resides. This type of transfer includes the following:

  • Transfers between Amazon EFS or FSx for Windows File Server file systems to Amazon storage in a different Amazon Web Services account.

  • Transfers from self-managed file systems to Amazon storage services.

Important

Deploy your agent such that it doesn't require network traffic between Availability Zones (to avoid charges for such traffic).

  • To access your Amazon EFS or FSx for Windows File Server file system, deploy the agent in an Availability Zone that has a mount target to your file system.

  • For self-managed file systems, deploy the agent in the Availability Zone where your file system resides.

To learn more about data transfer prices for all Amazon Web Services Regions, see Amazon EC2 On-Demand pricing.

For example, the following diagram shows a high-level view of the DataSync architecture for transferring data from in-cloud Network File System (NFS) to in-cloud NFS or Amazon S3.

Diagram showing data transfer between source Region containing a virtual private cloud (VPC) with an EFS file system and DataSync agent, and a destination Region with a DataSync endpoint and EFS file system.
Note

Deploy the agent in the Amazon Web Services Region and Amazon Web Services account where the source file system resides.

  • When you're copying between two Amazon EFS file systems in different Amazon Web Services accounts, we recommend that you use the NFS (source) to EFS (destination) transfer.

  • When you're copying between two Amazon FSx file systems in different Amazon Web Services accounts, we recommend that you use the Server Message Block (SMB) (source) to Amazon FSx (destination) transfer.

Transferring data from Amazon S3 to Amazon file systems

The following diagram provides a high-level view of the DataSync architecture for transferring data from Amazon S3 to an Amazon file system, such as Amazon EFS or Amazon FSx. You can use this architecture to transfer data from one Amazon Web Services account to another, or to transfer data from Amazon S3 to a self-managed in-cloud file system.

Diagram showing data transfer between source Region containing an S3 bucket and DataSync endpoint, and a destination Region containing a VPC with an EFS file system and DataSync agent.