Deploy your AWS DataSync agent - AWS DataSync

Deploy your AWS DataSync agent

An AWS DataSync agent is a virtual machine (VM) that you own. The type of agent you needs depends on the hypervisor you're using and where you're copying data (such as on-premises or cloud storage systems). You can reuse an agent if it can access your storage system and has been activated in the same AWS Region.

Deploy your agent on VMware

You can download an agent from the DataSync console and deploy it in your VMware environment.

Before you begin: Make sure that your storage environment can support a DataSync agent. For more information, see Virtual machine requirements.

To deploy an agent on VMware

  1. Open the AWS DataSync console at https://console.aws.amazon.com/datasync/.

  2. In the left navigation pane, choose Agents, and then choose Create agent.

  3. For Hypervisor, choose VMWare ESXi, and then choose Download the image.

    The agent downloads in a .zip file that contains an .ova image file.

  4. To minimize network latency, deploy the agent as close as possible to the storage system that will work with DataSync. For more information, see AWS DataSync network requirements.

    If needed, see your hypervisor's documentation on how to deploy an .ova file in a VMware host.

  5. Power on your hypervisor, log in to the agent VM, and get the agent's IP address. You need this IP address to activate the agent.

    The agent VM's default credentials are login admin and password password. If needed, change the password through the VM's local console.

Deploy your agent on KVM

You can download an agent from the DataSync console and deploy it in your KVM environment.

Before you begin: Make sure that your storage environment can support a DataSync agent. For more information, see Virtual machine requirements.

To deploy an agent on KVM

  1. Open the AWS DataSync console at https://console.aws.amazon.com/datasync/.

  2. In the left navigation pane, choose Agents, and then choose Create agent.

  3. For Hypervisor, choose Kernel-based Virtual Machine (KVM), and then choose Download the image.

    The agent downloads in a .zip file that contains a .qcow2 image file.

  4. To minimize network latency, deploy the agent as close as possible to the storage system that will work with DataSync. For more information, see AWS DataSync network requirements.

  5. Run the following command to install your .qcow2 image.

    virt-install \ --name "datasync" \ --description "DataSync agent" \ --os-type=generic \ --ram=32768 \ --vcpus=4 \ --disk path=datasync-yyyymmdd-x86_64.qcow2,bus=virtio,size=80 \ --network default,model=virtio \ --graphics none \ --import

    For information about how to manage this VM and your KVM host, see your hypervisor's documentation.

  6. Power on your hypervisor, log in to your VM, and get the IP address of the agent. You need this IP address to activate the agent.

    The agent VM's default credentials are login admin and password password. If needed, change the password through the VM's local console.

Deploy your agent on Microsoft Hyper-V

You can download an agent from the DataSync console and deploy it in your Microsoft Hyper-V environment.

Before you begin: Make sure that your storage environment can support a DataSync agent. For more information, see Virtual machine requirements.

To deploy an agent on Hyper-V

  1. Open the AWS DataSync console at https://console.aws.amazon.com/datasync/.

  2. In the left navigation pane, choose Agents, and then choose Create agent.

  3. For Hypervisor, choose Microsoft Hyper-V, and then choose Download the image.

    The agent downloads in a .zip file that contains a .vhdx image file.

  4. To minimize network latency, deploy the agent as close as possible to the storage system that will work with DataSync. For more information, see AWS DataSync network requirements.

    If needed, see your hypervisor's documentation on how to deploy a .vhdx file in a Hyper-V host.

    Warning

    You may notice poor network performance if you enable virtual machine queue (VMQ) on a Hyper-V host that's using a Broadcom network adapter. For information about a workaround, see the Microsoft documentation.

  5. Power on your hypervisor, log in to your VM, and get the IP address of the agent. You need this IP address to activate the agent.

    The agent VM's default credentials are login admin and password password. If needed, change the password through the VM's local console.

Deploy your agent as an Amazon EC2 instance

You can deploy a DataSync agent as an Amazon EC2 instance when copying data between:

Warning

We don't recommend using an Amazon EC2 agent to access your on-premises storage because of increased network latency. Instead, deploy the agent as a VMware, KVM, or Hyper-V virtual machine in your data center as close to your on-premises storage as possible.

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

    Example command and output

    aws ssm get-parameter --name /aws/service/datasync/ami --region us-east-1 { "Parameter": { "Name": "/aws/service/datasync/ami", "Type": "String", "Value": "ami-id", "Version": 6, "LastModifiedDate": 1569946277.996, "ARN": "arn:aws:ssm:us-east-1::parameter/aws/service/datasync/ami" } }

To deploy your DataSync agent as an Amazon EC2 instance

Important

To avoid charges, deploy your agent in a way that it doesn't require network traffic between Availability Zones. For example, deploy your agent in the Availability Zone where your self-managed file system resides.

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

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

    https://console.aws.amazon.com/ec2/v2/home?region=source-file-system-region#LaunchInstanceWizard:ami=ami-id

    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.

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

  3. On the Configure Instance Details page, do the following:

    1. For Network, choose the virtual private cloud (VPC) where your source Amazon EFS or NFS file system is located.

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

  4. Choose Next: Add Storage. The agent doesn't require additional storage, so you can skip this step and choose Next: Add tags.

  5. (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.

  6. On the Configure Security Group page, do the following:

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

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

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

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

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

Deploy your agent on AWS Snowcone

The DataSync agent AMI is pre-installed on your Snowcone device. Launch the agent with one of the following tools:

Deploy your agent on AWS Outposts

You can launch a DataSync Amazon EC2 instance on your Outpost. To learn more about launching an AMI on AWS Outposts, see Launch an instance on your Outpost in the AWS Outposts User Guide.

When using DataSync to access Amazon S3 on Outposts, you must launch the agent in a VPC that's allowed to access your Amazon S3 access point, and activate the agent in the parent Region of the Outpost. The agent must also be able to route to the Amazon S3 on Outposts endpoint for the bucket. To learn more about working with Amazon S3 on Outposts endpoints, see Working with Amazon S3 on Outposts in the Amazon S3 User Guide.