Amazon Elastic File System
User Guide

Amazon EFS File Sync

Using Amazon EFS File Sync, you can easily and efficiently sync files from an existing source file system into a destination Amazon EFS file system. The source file system can be on-premises or in the cloud. With EFS File Sync, you can migrate file-based applications to Amazon EC2 and sync existing datasets into Amazon EFS. EFS File Sync copies your file data, and file system metadata such as ownership, timestamps, and access permissions.


Unless otherwise noted, the following are required for creating Amazon EFS File Sync.

Hardware Requirements

When deploying Amazon EFS File Sync on-premises, you must make sure that the underlying hardware on which you are deploying the file sync VM is able to dedicate the following minimum resources:

  • Four virtual processors assigned to the VM.

  • 16 GB of RAM assigned to the VM

  • 80 GB of disk space for installation of VM image and system data

When deploying Amazon EFS File Sync on Amazon EC2, the instance size must be at least xlarge for your Amazon EFS File Sync to function. We recommend using one of the Memory optimized r4.xlarge instance types.

Supported Hypervisors and Host Requirements

You can choose to run EFS File Sync either on-premises as a virtual machine (VM), or in AWS as an Amazon Elastic Compute Cloud (Amazon EC2) instance.

EFS File Sync supports the following hypervisor versions and hosts:

  • VMware ESXi Hypervisor (version 4.1, 5.0, 5.1, 5.5, 6.0 or 6.5)—A free version of VMware is available on the VMware website. You will also need a VMware vSphere client to connect to the host.

  • EC2 instance—EFS File Sync provides an Amazon Machine Image (AMI) that contains the EFS File Sync VM image. We recommend using the Memory optimized r4.xlarge instance types.

EFS File Sync End Points

The following endpoints are required by EFS File Sync.

cp-sync.$ api-sync.$ activation-sync.$

For information about supported AWS Regions, see Amazon Elastic File System in the AWS General Reference.

EFS File Sync Architecture

EFS File Sync provides the following benefits:

  • Efficient high-performance parallel data transfer that tolerates unreliable and high-latency networks.

  • Encryption of data transferred from your IT environment to AWS.

  • Data transfer rate up to five times faster than standard Linux copy tools.

The following diagram shows the EFS File Sync architecture.

To sync your existing file system to Amazon EFS with EFS File Sync, you do the following:

  1. Deploy a sync agent that can mount your source file system. The sync agent is available on the Amazon EFS console as a downloadable virtual machine (VM) image for VMware ESXi or an Amazon Machine Image (AMI) for Amazon EC2.

  2. Create a sync task and configure the source and destination file systems. EFS File Sync accesses your source file system through the agent by using the Network File System version 3.0 or 4.0 (NFSv4 or v3) protocol.

  3. Start your sync task to begin syncing files from the source file system to the destination Amazon EFS file system.

  4. Monitor the progress of your sync task on the Amazon EFS Management Console or from Amazon CloudWatch.