Deploy your Amazon DataSync agent
Amazon DataSync provides agents for various storage environments. You can deploy your agent on a VMware ESXi, Linux Kernel-based Virtual Machine (KVM), or Microsoft Hyper-V hypervisor. For storage in a virtual private cloud (VPC) in Amazon, you can deploy an agent as an Amazon EC2 instance.
Topics
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
Open the Amazon DataSync console at https://console.amazonaws.cn/datasync/
. -
In the left navigation pane, choose Agents, and then choose Create agent.
-
For Hypervisor, choose VMWare ESXi, and then choose Download the image.
The agent downloads in a
.zip
file that contains an.ova
image file. -
To minimize network latency, deploy the agent as close as possible to the storage system that DataSync needs to access (the same local network if possible). For more information, see Amazon DataSync network requirements.
If needed, see your hypervisor's documentation on how to deploy an
.ova
file in a VMware host. -
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 passwordpassword
. 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
Open the Amazon DataSync console at https://console.amazonaws.cn/datasync/
. -
In the left navigation pane, choose Agents, and then choose Create agent.
-
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. To minimize network latency, deploy the agent as close as possible to the storage system that DataSync needs to access (the same local network if possible). For more information, see Amazon DataSync network requirements.
-
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.
-
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 passwordpassword
. 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
Open the Amazon DataSync console at https://console.amazonaws.cn/datasync/
. -
In the left navigation pane, choose Agents, and then choose Create agent.
-
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. -
To minimize network latency, deploy the agent as close as possible to the storage system that DataSync needs to access (the same local network if possible). For more information, see Amazon 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
. -
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 passwordpassword
. If needed, change the password through the VM's local console.
Deploy your agent on Amazon EC2
You can deploy a DataSync agent as an Amazon EC2 instance when copying data between:
-
A self-managed cloud storage system and an Amazon storage service.
For more information about these use cases, including high-level architecture diagrams, see Deploying your Amazon DataSync agent in an Amazon Web Services Region.
-
A cloud storage provider (such as Google Cloud Storage or Microsoft Azure Blob Storage) and an Amazon storage service.
-
Amazon S3 on Amazon Outposts and an Amazon storage service.
Warning
We don't recommend using an Amazon EC2 agent with 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 Amazon Web Services Region
-
Use the following Amazon CLI command to get the latest DataSync Amazon Machine Image (AMI) ID for your Amazon Web Services 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-cn: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 Amazon Web Services Regions, see
Amazon EC2 On-Demand
pricing
-
From the Amazon Web Services 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.amazonaws.cn/ec2/v2/home?region=
source-file-system-region
#LaunchInstanceWizard:ami=ami-id
In the URL, replace the
andsource-file-system-region
with your own source Amazon Web Services Region and AMI ID.ami-id
-
For Instance type, choose one of the recommended Amazon EC2 instances for DataSync.
-
For Network settings, choose Edit and then do the following:
-
For VPC, choose the virtual private cloud (VPC) where the storage system you're transferring data to or from is located.
-
For Auto-assign public IP, choose whether you want your agent to be accessible from the public internet.
You use the instance's public or private IP address later to activate your agent.
-
For Firewall (security groups), create or a select a security group that does the following:
-
Allows inbound traffic from your web browser to the instance on port 80 (HTTP).
-
Allows inbound and outbound traffic between the instance and your storage system. For more information, see Network requirements for self-managed and other cloud storage.
Note
You will need to configure additional ports depending on the type service endpoint that you use to connect the agent with Amazon.
-
-
-
(Recommended) To increase performance when transferring from a cloud-based file system, expand Advanced details choose a Placement group value where your storage resides.
-
Choose Launch to launch your instance.
-
Once your instance status is Running, choose the instance.
-
If you configured your instance to be accessible from the public internet, make note of the instance's public IP address. If you didn't, make note of the private IP address.
You need this IP address when activating your agent.
Deploy your agent on Amazon 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 Amazon Outposts
You can launch a DataSync Amazon EC2 instance on your Outpost. To learn more about launching an AMI on Amazon Outposts, see Launch an instance on your Outpost in the Amazon 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.