The following is a summary of requirements that should be met for an AWS environment and instances created on it.
Requirements for AWS Environment
Create a base environment on AWS to provide services. The requirements for using this configuration are as follows.
Amazon Virtual Private Cloud (VPC)
- VPC needs to be configured in AWS.
- The subnet where the primary instance is located and the subnet where the standby instance is located must be created in different Availability Zones (AZ).
Amazon Elastic Compute Cloud (EC2)
- At least 2 instances are required.
- A primary instance and a standby instance need to be configured to start with different AZ for each.
- Instances are connected to Elastic Network Interface (ENI).
- Instances are required to satisfy LifeKeeper’s installation requirements.
- The AWS Command Line Interface (AWS CLI) needs to be installed in each of EC2 the instances. For the details, please refer to AWS Command Line Interface installation.
- You need to be able to access Amazon EC2 Web Services endpoint URL (EC2 URL) using https and Amazon EC2 metadata URL (http://169.254.169.254/) using http.
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. Cconfigure an EC2 IAM role or configure AWSCLI appropriately so that it can be accessed from root user of the EC2 instance.
AWS Transit Gateway
- The VPC with the cluster nodes and the on-premises environment where the clients are located must be connected via AWS Transit Gateway; not via Virtual Private Gateway.
- Enable the Default route table association and the Default route table propagation when creating AWS Transit Gateway.
- Connect VPC by creating Transit Gateway Attachment.
- Connect to AWS Direct Connect by selecting the created AWS Transit Gateway in the Gateway association configuration of Direct Connect Gateway. At this time, configure both the network address of the VPC where the cluster nodes are located and the virtual IP address in Allowed prefixes.
LifeKeeper Software Requirements
You need to install the same version of LifeKeeper software and patches on each server. The Application Recovery Kit (ARK) required for this configuration is shown below. For the specific LifeKeeper requirements, please refer to: LifeKeeper for Linux Technical Documentation and LifeKeeper for Linux Release Notes
- LifeKeeper IP Recovery Kit
- LifeKeeper Recovery Kit for EC2