Deleting your AWS DataSync agent - AWS DataSync
Deleting a DataSync agentReusing a DataSync agent

Deleting your AWS DataSync agent

When you delete an agent from AWS DataSync, the agent resource is no longer associated with your AWS account and can't be undone.

Keep in mind that deleting an agent from DataSync doesn't remove its virtual machine (VM) or Amazon EC2 instance from your storage environment. You can delete the VM or instance or reuse it to activate a new agent.

Deleting a DataSync agent

Before you begin

Don't delete an agent until you update or remove the DataSync resources that depend on it. If you're replacing an agent, update your transfer locations with the new agent. If you aren't replacing an agent, delete transfer tasks and locations using that agent first.

To delete an agent

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

  2. In the left navigation pane, choose Agents.

  3. Choose the agent that you want to delete.

  4. Choose Delete, enter delete in the text box that appears, and then choose Delete.

  5. If you aren't planning to reuse the agent, delete the agent's VM or Amazon EC2 instance to remove it from your storage environment.

Reusing a DataSync agent

You can delete an agent resource from DataSync and still use the agent's underlying VM or Amazon EC2 instance to activate a new agent.

To reuse an agent

  1. Test the agent's connection to AWS. If the network tests pass, go to the next step.

    The network tests must pass before you can move to the next step.

  2. Delete the agent resource from DataSync but don't delete the agent's VM or Amazon EC2 instance.

  3. Repeat step 1 to test the agent's connection to AWS again. If the network tests pass, go to the next step.

  4. About three minutes after deleting the agent resource from DataSync, check if port 80 is open on the agent VM or Amazon EC2 instance. If it is, go to the next step.

  5. Activate a new agent with the existing VM or Amazon EC2 instance.

    You can activate the new agent in a different AWS Region, AWS account, and with another type of service endpoint. If you use a different type of service endpoint, you have to adjust your network configuration.