This document provides a step-by-step guide to replicating data from on-premise to cloud using AWS DataSync. It outlines setting up the necessary infrastructure components like creating a VPC, S3 bucket, security groups, and deploying the DataSync agent on an EC2 instance. It then walks through creating a DataSync task to copy files from S3 to an EFS file system, mounting the EFS on another EC2 instance to verify the files were successfully copied.

1. AWS DataSync – A step by step implementation guide.
How to replicate data from on-premise to cloud, between various clouds, and between different
regions within a cloud using AWS DataSync.

2. Create the VPC:

3. Create the S3 bucket:
Load files into S3 bucket:
Create a SecurityGroup(SG) with port 80, 443, and 22 open for 0.0.0.0/0:

5. Deploy the DataSync agent on an EC2 instance in the public subnet with the public IP enabled in
the same region (eu-west-1):

6. To deploy the agent
 Install the AWS CLI (if you don’t have it). You will get the detail instruction here
https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html
 To choose the agent AMI for your AWS Region
Use the following CLI command to get the latest DataSync Amazon Machine Image
(AMI) ID for the specified AWS Region.
aws ssm get-parameter --name /aws/service/datasync/ami --region region
You will get all the details here
https://docs.aws.amazon.com/datasync/latest/userguide/deploy-agents.html#create-
vmw-agent

7. From the AWS account where the source file system resides, launch the agent by using your
AMI from the Amazon EC2 launch wizard. Use the following URL to launch the AMI.
In the URL, replace the source-file-system-region and ami-id with your own source AWS Region
and AMI ID. The Choose an Instance Type page appears on the Amazon EC2 console.
https://console.aws.amazon.com/ec2/v2/home?region=source-file-system-
region#LaunchInstanceWizard:ami=ami-id
https://console.aws.amazon.com/ec2/v2/home?region=eu-west-
1#LaunchInstanceWizard:ami=ami-04e369d8cf2c50c5a
1. Choose one of the recommended instance types for your use case, and choose Next: Configure
Instance Details. For the recommended instance types, see Amazon EC2 instance
requirements.
2. On the Configure Instance Details page, do the following:
a. For Network, choose the virtual private cloud (VPC) where your source Amazon EFS or NFS file
system is located.

8. b. For Auto-assign Public IP, choose a value. For your instance to be accessible from the public
internet, set Auto-assign Public IP to Enable. Otherwise, set Auto-assign Public IP to Disable. If a
public IP address isn't assigned, activate the agent in your VPC by using its private IP address.
When you transfer files from an in-cloud file system, to increase performance we recommend
that you choose a Placement Group value where your NFS server resides.
3. Choose Next: Add Storage. The agent doesn't require additional storage, so you can skip this
step and choose Next: Add tags.
4. (Optional) On the Add Tags page, you can add tags to your Amazon EC2 instance. When you're
finished on the page, choose Next: Configure Security Group.
5. On the Configure Security Group page, do the following:
a. Make sure that the selected security group allows inbound access to HTTP port 80 from the
web browser that you plan to use to activate the agent.
b. Make sure that the security group of the source file system allows inbound traffic from the
agent. In addition, make sure that the agent allows outbound traffic to the source file system. If
you deploy your agent by using a VPC endpoint, you need to allow additional ports. For more
information, see How DataSync works with VPC endpoints .
For the complete set of network requirements for DataSync, see AWS DataSync network
requirements.
6. Choose Review and Launch to review your configuration, then choose Launch to launch your
instance. Remember to use a key pair that's accessible to you. A confirmation page appears
and indicates that your instance is launching.
7. Choose View Instances to close the confirmation page and return to the Amazon EC2 instances
screen. When you launch an instance, its initial state is pending. After the instance starts, its
state changes to running. At this point, it's assigned a public Domain Name System (DNS) name
and IP address, you can find these in the Descriptions tab.
8. If you set Auto-assign Public IP to Enable, choose your instance and note the public IP address
in the Description tab. You use this IP address later to connect to your sync agent.
If you set Auto-assign Public IP to Disable, launch or use an existing instance in your VPC to
activate the agent. In this case, you use the private IP address of the sync agent to activate the
agent from this instance in the VPC.

11. EC2 instance with the DataSync agent:

13. DataSync agent is created.
Create a new security group with inbound port 2049 open to launch an Amazon EFS (Elastic File
System) in your VPC, and create a file system.

14. Create an EFS file system:

17. Create a DataSync task:

23. Start the task:

25. Launch a new EC2 instance to check the files (which are copied from S3) in the EFS:

27. Connect to the EC2 instance and run yum update:

28. Mount the EFS to this newly created EC2 instance:
https://docs.aws.amazon.com/efs/latest/ug/mounting-fs-mount-helper-ec2-linux.html
Create a directory efs that you will use as the file system mount point using the following
command:

29. To mount using the file system id:
sudo mount -t efs file-system-id efs-mount-point/
sudo mount -t efs fs-0f33bf88395c3d357 efs/

30. All files successfully copied from S3 to EFS!