Using the DataSync EC2 agent deployed in AWS Regions - AWS DataSync

Using the DataSync EC2 agent deployed in AWS Regions

This section describes data transfer between in-cloud file systems and Amazon S3 buckets using the DataSync EC2 agent.

Note

To transfer files or objects between datasets in Amazon S3, Amazon EFS, or Amazon FSx in the same AWS account, you don't need to deploy a DataSync agent. To learn more, see Data transfer between AWS storage services.

You can use the DataSync EC2 agent deployed in an AWS Region to transfer data between in-cloud file systems and Amazon S3 in different accounts, or between self-managed in-cloud file systems and Amazon S3.

For more information about deploying a DataSync EC2 agent in a Region, see Deploy your agent as an EC2 instance to access in-cloud file systems.

Data transfer from in-cloud file system to in-cloud file system or Amazon S3

To transfer data from one AWS account to another, or from a self-managed in-cloud file system, the DataSync agent must be located in the same AWS Region and same AWS account where the source file system is deployed. This type of transfer includes the following:

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

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

Important

Deploy your agent such that it does not require network traffic between Availability Zones (to avoid charges for such traffic).

  • To access your Amazon EFS or Amazon 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 AWS 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 NFS to in-cloud NFS or Amazon S3.


                    Diagram showing data transfer between source Region containing a 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 AWS Region and AWS account where the source file system resides.

  • When you're copying between two Amazon EFS file systems in different AWS 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 AWS accounts, we recommend that you use the SMB (source) to Amazon FSx (destination) transfer.

Data transfer from S3 to in-cloud file systems

The following diagram provides a high-level view of the DataSync architecture for transferring data from Amazon S3 to an in-cloud file system. You can use this architecture to transfer data from one AWS 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.