Skip to main content
Restoring AMIs
Updated over a week ago


An Amazon Machine Image (AMI) is a template that contains a software configuration (for example, an operating system, an application server, and applications). From an AMI, you can launch an instance, which is a copy of the AMI running as a virtual server in the cloud. For example, the AMI is an image of your EC2 instance. You can restore an EC2 instance backed up to Druva Cloud from the storage region specified in the backup policy.

Restoring AMIs

To restore an AMI:

  1. Log into your management console and navigate to Resources > EC2.

  2. Navigate to the Backups tab and select the AMI that you wish to restore.

  3. On the backup details page, click Restore.
    Alternatively, you may select the AMI from the Backups page, and then click Restore to initiate the restore process.



Instance Name

By default, Druva CloudRanger displays the name of the original EC2 instance, and if unavailable, the instance ID is used as the name. You can choose to modify the default instance name.


The AWS Region where the backed-up AMI is stored.

Availability Zone

Choose an availability zone within the region where the AMI is stored.
For more information, see Regions and Availability Zones

Instance Type

Choose an instance type of the restored EC2 instance. By default, Druva CloudRanger selects the original EC2 instance type.

📝 Note
Not all instance types are supported in all regions. If you run into issues with the restore, verify that the selected instances are supported for that region.

For more information, refer to the AWS documentation.

Windows Marketplace AMI

Enable the toggle if you are attempting to restore a marketplace Windows AMI.



This section displays the tag keys that have been specified for the source EC2 instance or the AMI.
Tags act as metadata to help identify and organize your AWS resources.


The Value will depend on the Key specified.
Key: Created by Policy; Value: New
Key: Origin; Value: Origin ID



Select a virtual private cloud (VPC) where you want the restored EC2 instance to run.


Select the subnet of the VPC where you want the restored EC2 instance to run.


Select the virtualization type for the restored EC2 instance.

Private IP

Specify the private IP address of the EC2 instance that will be attached to it upon restore. The IP address provided must be within the range of IP addresses for the Subnet specified previously.


Key Name

The backup encryption target key for the EC2 instance.
If you plan on remotely connecting to the restored EC2 instance, select a key pair created in your account.

Instance Profile

Choose an instance profile for the restored EC2 instance.

Security Groups

Select a security group for the restored EC2 instance.

Block Device Mappings

This section displays information on the AMI to be restored:

  • Device Name and Snapshot ID

  • Delete On Termination

  • Encrypted: Policy-based backup encryption, if applicable

  • Volume Size and Volume Type of the AMIs to be restored

4. Click Confirm.
The restored AMIs will now be available on the Restores page.

Restoring AMIs with File Level Recovery

With the file-level recovery functionality, you can initiate a recovery instance within Druva’s environment and choose the files you want to recover.

This launches an instance and runs Druva's FLR agent, which virtually mounts the chosen point-in-time backup and serves a browsable view of files/folders to restore. Upon initiating a restore, the FLR instance zips the selected files into a single zip archive, which are accessible via the S3 bucket in your source AWS account.

Before you begin

To enable this feature, you will need to update your AWS Access Role by deploying the latest CloudFormation template for each account in which you intend to leverage file level recovery. For more information, see Update Existing AWS Access Roles in Druva CloudRanger.


To initiate a file-level recovery:

  1. Log into your management console and navigate to Resources > EC2.

  2. Navigate to the Backups tab and select the AMI that you wish to restore.
    Note: Set the Location filter to Druva Cloud to view all backups on Druva Cloud.

  3. On the backup details page, click Restore. Alternatively, select the snapshot from the Backup page, and then click Restore.

  4. On the Restore dialog, select File level recovery.


The restore once initiated launches an instance in Druva’s managed infrastructure.

5. Navigate to the browse view presented and select the file(s) to be restored.


Once initiated, the instance is created only with the selected files and folders, and the instance is discarded after 2 hours.

6. Navigate to your Jobs Restore page to track the restore job.
7. A link to the restored files is presented on the Restores page, which will redirect you to the file location within the S3 bucket of your AWS account.

Once the instance becomes available, locate the archived files for downloading. You may also download a directory with one click using the download icons on the right, which will download the archive with a .zip extension.

Did this answer your question?