Configuring an Amazon EC2 Instance as an Agentless File Recovery Destination

You can restore files and folders directly to the original instance or a different instance, from streaming or IntelliSnap backups of Windows or Linux instances. The destination instance or guest instance must be running.

This feature is supported only in the Command Center.

You can use a Windows or Linux access node.

Before You Begin

The destination instance must be running.


Perform the following operations on the destination instance:

  1. Install AWS Systems Manager (SSM) on the instance if it is not already installed.

    In AWS, SSM is installed by default on instances that run Windows Server 2016 and more recent versions of Windows Server.

    For Windows Server 2003 to Windows Server 2012 R2, SSM is installed by default on instances created from AMIs published in November 2016 and more recently.

  2. Attach an IAM role with the AmazonEC2RoleforSSM managed policy to the Amazon instance.

  3. Install PowerShell Core:

  4. Install AWS Tools for PowerShell Core:

  5. To verify that the instance can be used as a destination for agentless file recovery, perform the following steps:

    1. From the AWS Console, navigate to SYSTEMS MANAGER SERVICES > Run Command.

    2. Click Run a command.

    3. From Manage your Instances, click Run a command.

    4. Select AWS-RunPowerShellScript.

    5. In the Select Targets by section, click Select instances.

    The instances that are displayed can be used as destinations for agentless file recovery.

Agentless Restore Process

When performing an agentless restore, the software uses the following process:

  1. Restore the data to the access node.

  2. If an Amazon S3 bucket does not already exist, create one.

  3. Upload the data to the Amazon S3 bucket.

  4. Download the data to the destination instance.

  5. Delete the temporary data from the Amazon S3 bucket and the access node.