# Manually Deploying an Amazon EC2 Instance After a Restore Fails

When a restore of an Amazon EC2 instance fails during the deployment phase, the disks or the AMI are retained. You can use the retained resources to manually deploy the instance in the AWS portal.

If the job status is "Completed with Errors" and the instance status is "Partial success", the Failure reason column for the instance displays "Failed to deploy VM with reason".

## Step 1: Get the EBS Volume IDs

1. Go to the specific job. From the Command Center navigation pane, go to Jobs > Job history.

   The Job history page appears.

2. Click the failed restore job.

   The Job details page appears. The Failure reason column includes the information for the failed instance deployment.

3. On the Instance list tab, click the action button in the upper-right corner of the page, and then click View failed items.

   The Failed items list appears. The information includes information about the retained resources such as EBS volumes with their IDs.

## Step 2: Attach the EBS Volumes to an Existing EC2 Instance, or Deploy a New EC2 Instance

- To attach the volumes to an existing EC2 intance, see Attach an Amazon EBS volume to an Amazon EC2 instance.

- To deploy a new EC2 instance, in the AWS portal, do the following:

  1. Use the volume IDs to find the EBS volumes.

  2. Create a snapshot from the volume.

  3. Create an AMI from the snapshot.

  4. Find the AMI in your private images.

  5. From the AMI, create a new EC2 instance. For instructions, see Create an EC2 instance from an imported image.

     The values that you need to create the EC2 instance are on the Job details page of the failed job.

  6. After the EC2 instance is created, attach the EBS volumes (other than the root volume) to the instance. For instructions, see Attach an Amazon EBS volume to an Amazon EC2 instance.

×

Loading...