Recovery Kit for EC2™ Operations Overview

Each operation is performed based on the AWS CLI provided by Amazon Web Services.

The Recovery Kit for EC2 works differently depending on the resource type specified during resource creation. Please refer to the following depending on the resource type you are using.

• Route Table scenario (Backend Cluster)
• Elastic IP scenario (Frontend cluster)

Bringing a Resource In Service (restore)

Perform the following operations for each scenario when the EC2 resource is brought in service.

Route Table scenario (Backend Cluster)

1. Obtain the route table information.
2. Update the route table.

Elastic IP scenario (Frontend cluster)

1. Obtain the Elastic Network Interface (ENI).
2. Associate an elastic IP with the ENI.
3. Make sure that the NIC is linked up.
   If not, link up the NIC.
4. Check the association between Elastic IP and ENI.

If there is no response from the AWS CLI, it will timeout with the value of EC2_RESTORE_TIMEOUT (default : 300 seconds).

Taking a Resource Out of Service (remove)

Perform the following operations for each scenario when the EC2 resource is taken out of service.

Route Table scenario (Backend Cluster)

In this scenario, there are no steps related to EC2 resources.

Elastic IP scenario (Frontend cluster)

Unassociate the ENI ID from the Elastic IP and
confirm that they are no longer associated.

If there is no response from the AWS CLI, it will timeout with the value of EC2_REMOVE_TIMEOUT (default : 300 seconds).

Monitoring (quickCheck)

When monitoring EC2 resources, perform the following steps for each scenario.

Route Table scenario (Backend Cluster)

Confirm that the ENI on the active node is correct.

Elastic IP scenario (Frontend cluster)

Confirm the ENI and Elastic IP association and link up on the active node.

If there is no response from AWS CLI, it will timeout with the value of EC2_QUICKCHECK_TIMEOUT (default : 100 seconds).
A timeout is not considered a resource failure.
If it is determined to be abnormal based on the results obtained using the AWS CLI and the metadata information on the node, it should be a resource failure.

Recovery (recover)

When recovering EC2 resources, perform the following steps for each scenario.

Route Table scenario (Backend Cluster)

Execute the same process as restore.

Elastic IP scenario (Frontend cluster)

Execute the same process as restore.

If there is no response from the AWS CLI, it will timeout with the value of EC2_RECOVER_TIMEOUT (default : 300 seconds).

Recovery Kit for EC2 Parameters

For more details on the Recovery Kit for EC2 parameters described here, see EC2 Parameters List .