Some requirements should be met when using this configuration. Below is a summary of requirements for the 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)
- Two or more VPCs must be created.
VPCs can be created either in the same region or different regions.
- VPCs must be connected using a VPC peering connection.
If more than three VPCs are created, either connect each VPC with VPC peering, or connect each VPC in a star configuration via AWS Transit Gateway.
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 or different VPC for each.
- EC2 Instances are connected to Elastic Network Interface (ENI).
- EC2 Instances are required to satisfy LifeKeeper’s installation requirements.
- AWS Command Line Interface (AWS CLI) needs to be installed in each of EC2 the instances. For the details, please refer to Installing or updating the latest version of the AWS CLI.
- Instances need to have access to route53.amazonaws.com with HTTPS protocol. Please configure EC2 and the OS properly
AWS Identity and Access Management (IAM)
In order for LifeKeeper for Linux to operate in AWS, an IAM user or IAM role with the following access privilege is required. Please configure an Amazon EC2 IAM role or configure AWS CLI appropriately so that it can be accessed from the root user of the EC2 instance.
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.