Before attempting to install or remove the Recovery Kit for EC2™ you must understand Amazon Web Service software requirements, as well as the installation and removal procedures for the Recovery Kit for EC2™ package.
Amazon Web Service and Software Requirements
Before installing and configuring the Recovery Kit for EC2™, be sure that your configuration meets the following requirements:
Amazon Virtual Private Cloud (VPC):
• The recovery kit requires a VPC be configured within AWS
• Two or more Subnets created on different Availability Zones (AZ)
• Each Subnet contains associated Route Tables
• If you are configuring a Public (Frontend) Cluster, then one or more Elastic IPs must be allocated
Amazon Elastic Compute Cloud (EC2™):
• The recovery kit requires two or more EC2™ instances.
• The instances are associated on each Subnet.
• The instances are attached to an Elastic Network Interface (ENI).
• If creating a Route Table (backend cluster) resource, each instance should have its network source/destination checks disabled.
• All the EC2 instances must be able to access Amazon EC2™ services endpoints (AWS Regions and Endpoints) using the protocols HTTP and HTTPS. Please configure Recovery Kit for EC2™ and the OS properly.
• In order to obtain metadata of Amazon EC2™ instances, it is necessary to have an access to IP address 169.254.169.254 using the HTTP protocol.
• AWS Command Line Interface version 2 (AWS CLI v2) needs to be installed on each of the EC2™ instances. For the details, please refer to AWS Command Line Interface version 2 Installation.
• Since the AWS CLI v2 is used, outbound connections on TCP port 443 must be enabled.
• Since the Auto Recovery function may conflict with the recovery function of LifeKeeper, it is not recommended to use these functions together.
Note: If the path name of AWS CLI v2 executable files is not specified on the “PATH” parameter in the LifeKeeper defaults file %LKROOT%\etc\default\LifeKeeper, you must append the path name of AWS CLI v2 executable files to the “PATH” parameter.
AWS Identity and Access Management (IAM):
In order for LifeKeeper to operate AWS, an IAM user or IAM role with the following access privilege is required. Please configure an EC2™ IAM role or configure AWS CLI v2 appropriately so that it can be accessed from root user of the EC2™ instance.
Route Table (backend) configuration:
Elastic IP (frontend) configuration:
You must install the same version of LifeKeeper software and any patches on each server. Please refer to the LifeKeeper for Windows Technical Documentation and the LifeKeeper for Windows Release Notes for specific LifeKeeper requirements.
LifeKeeper Recovery Kit for EC2™:
You must install the same version of Recovery Kit for EC2™ software and any patches on each server.
LifeKeeper IP Recovery Kit:
If you are using the Recovery Kit for EC2™ to provide protection for the Route Table (Backend Cluster), you must install the same version of LifeKeeper for Windows IP Recovery Kit software and any patches on each server.
Note: The netmask of IP resources used should be 32 bits (255.255.255.255).
Note: The virtual IP must be outside of the VPC subnet (i.e. for a VPC network of 10.0.0.0/16 a virtual IP in the 10.1.0.0/16 subnet is needed – 10.1.0.100/32 would be appropriate).
Note: Please refer to the LifeKeeper for Windows Release Notes or your sales representative for the latest release compatibility and ordering information. You should refer to the LifeKeeper for Windows Installation Guide for specific instructions on how to install or remove the LifeKeeper Recovery Kit for EC2™.