This document descries the requirements and basic operations for building connections among VPCs with LifeKeeper for Linux for v9.5.0.
You can also build HA clusters in the AWS environment using the existing Recovery Kit for EC 2; however, you cannot connect from your on-premises environment with AWS Direct Connect due to the problems described below.
Recovery Kit for EC2 provides two functions: “Route Tables Scenario” and “Elastic IP Scenario.”
“Route Tables Scenario” manages VPC route tables are configured to be routed to an active IP resources. An address of IP resource should be outside CIDR block which is managed within the VPC. However, the address should be the one within the VPC CIDR block in order to connect from other VPC via VPC Peering Connection. With this route table scenario, you cannot connect to the
VPC from the on-premises environment.
“Elastic IP Scenario” can be used where the access from the Internet is available since the elastic IP address is a public address. An access from the on-premises environment is enabled through the Internet. In this case, you can access to HA cluster nodes on VPC without VPC Peering Connection.
For above reasons, Recovery kit for EC2 does not support an access to VPC from other VPC using VPC Peering Connection. If you need to access to HA cluster nodes on the VPC via VPC Peering Connection, please use the configuration provided in this document.
Please note that this document does not describe the basic settings, operations, and technical details of LifeKeeper and Amazon Web Service (AWS). For terms, operations and technical information related to LifeKeeper and AWS, that are the prerequisites of this configuration, please read related documents and user websites beforehand.
Post your comment on this topic.