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.
- Need to create more than two subnets 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.
- Instances need to have access to route53.amazonaws.com using the HTTPS protocol. Please configure EC2 and the OS to support this access requirement.
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 AWSCLI appropriately so that it can be accessed from root user of the EC2 instance.
Following access privileges are also required when using Recovery Kit for EC2:
Amazon Route 53
- You need to register your domain name on Amazon Route 53 to use the service. This is required to create a Route53 resource.
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: SPS for Linux Technical Documentation and SPS for Linux Release Notes
- LifeKeeper IP Recovery Kit
- LifeKeeper Route53 Recovery Kit
Requirements for using this service from your on-premises environment or other VPCs are as follows:
- Clients using the service should be able to resolve names of the hosts that are protected by Route53 resources.
- Clients using the service should access with the host name protected by Route53 resource.