Creating and Activating an Agent - AWS DataSync

Creating and Activating an Agent

After you deploy an agent into your VMware ESXi or Amazon EC2 environment, activate the agent. Activate your agent in the AWS Region where the Amazon S3 bucket, Amazon EFS, or Amazon FSx for Windows File Server file system that you plan to use with DataSync resides. The activation process associates your agent with your AWS account in the most secure way available. After the agent is successfully activated, DataSync closes the agent's port 80.

All data transferred between the agent and AWS is encrypted with Transport Layer Security (TLS). A DataSync agent can communicate with AWS by using one of the following:

  • Connecting to a public serivce endpoint – Data is transferred over the public internet.

  • Connecting to a private virtual private cloud (VPC) endpoint – Data is transferred within your VPC, without crossing the public internet, to increase the security of the copied data.

    For more information about activating an agent with a private VPC endpoint, see Using AWS DataSync in a Virtual Private Cloud.

  • Connecting to a Federal Information Processing Standard (FIPS) endpoint – Data is transferred over the public internet using processes that comply with Federal Information Processing Standards (FIPS).

Your agent is managed by AWS, and AWS automatically updates it without interrupting your tasks. To access the agent's local console, see Logging In to the AWS DataSync Local Console. For security reasons, you can't use Secure Shell (SSH) to access the agent or remotely connect to the agent's local console.

For the agent to work properly, make sure that your network is configured properly. For information on network requirements, see Network Requirements for DataSync. You can use the VM's local console to test for internet connectivity. For more information, see Testing Your Agent Connection to the Internet.

In some cases, an agent is activated but isn't functioning properly. This issue can come from problems with a network partition, firewall misconfiguration, or other events that mean the agent VM can't connect to AWS. For information about how to troubleshoot connectivity and activation issues, see Testing Your Agent Connection to the Internet.

For instructions on how to create an agent on a VMware ESXi host, see Deploy Your DataSync Agent on VMware.

For instructions on how to create an agent on an Amazon EC2 instance, see Deploy Your Agent as an EC2 Instance to Read Files from In-Cloud.