Menu
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.

Requirements for EFS File Sync

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.

Allowing EFS File Sync Access through Firewalls and Routers

EFS File Sync requires access to the following endpoints to communicate with AWS. If you use a firewall or router to filter or limit network traffic, you must configure your firewall and router to allow these service endpoints for outbound communication to AWS.

The following endpoints are required by EFS File Sync.

cp-sync.$region.amazonaws.com activation-sync.$region.amazonaws.com ec2-*.amazonaws.com

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

The CloudFront endpoint is required prior to activation for the sync agent to get the list of available AWS Regions.

https://d4kdq0yaxexbo.cloudfront.net/

Network and Port Requirements

EFS File Sync requires the following ports for its operation. This section shows an illustration of the required ports and lists the ports required by EFS File Sync.

The following illustration shows the ports to open for EFS File Sync deployed on premise.

Ports required by EFS File Sync

From

To

Protocol

Port

How Used

EFS File Sync VM

AWS

TCP

443 (HTTPS)

For communication from EFS File Sync VM to the AWS service endpoint. For information about service endpoints, see Allowing EFS File Sync Access through Firewalls and Routers.

Your Web browser

EFS File Sync VM

TCP

80 (HTTP)

By local systems to obtain the sync agent activation key. Port 80 is only used during activation of the EFS File Sync agent.

EFS File Sync VM does not require port 80 to be publicly accessible. The required level of access to port 80 depends on your network configuration. If you activate your sync agent from the Amazon EFS Management Console, the host from which you connect to the console must have access port 80.

EFS File Sync VM

Domain Name Service (DNS) server

UDP/UDP

53 (DNS)

For communication between EFS File Sync VM and the DNS server.

EFS File Sync VM

AWS

TCP

22 (Support channel)

Allows AWS Support to access your EFS File Sync to help you with troubleshooting EFS File Sync issues. You don't need this port open for the normal operation, but it is required for troubleshooting.

EFS File Sync VM

NTP server

UDP

123 (NTP)

Used by local systems to synchronize VM time to the host time.

NFS client

EFS File Sync VM

TCP/UDP

2049 (NFS)

For local systems to connect to NFS shares EFS File Sync exposes.

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 4.1 (NFSv4.1) 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.