Generic ARK for AWS Transit Gateway Configuration

Creating an IP Resource

Create and extend an IP resource to protect the virtual IP, and start it on the primary node. For specific instructions, refer to Creating an IP Resource Hierarchy.
When extending an IP resource using the LKCLI, specify the --ipaddr option. For specific instructions, refer to Setting up IP from the Command Line (LKCLI).

Configuring the Route Table of VPCs

Add the following entries to the route table of each VPC where cluster nodes and clients are located.

Route table of the VPC (local VPC) where the primary node is located

The route table of the VPC (remote VPC) where the standby node or client is located

For the VPC where cluster nodes are located, apply the above settings to the main route table. After that, you may also apply the above settings to the subnet route tables.
For the VPC where only clients are located, the above settings may be applied either to the VPC’s main route table or to the subnet route tables.

Configuring the Route Table of Transit Gateway

Add the following entries to the route table of the Transit Gateway attached to each VPC where cluster nodes and clients are located.

The route table of the Transit Gateway attached to the VPC where the primary node is located

The route table of the Transit Gateway attached to the VPC where the standby node or client is located

With the settings up to this point, verify that you can connect to the primary node from each cluster node and from each client using the virtual IP address.

Creating a Generic ARK for AWS Transit Gateway Resource

Create the Generic ARK for AWS Transit Gateway resources by following the steps below.

1. Select Create Resource Hierarchy from the LifeKeeper GUI to launch the Create Resource Wizard. On the Recovery Kit selection screen, choose Generic Application.
2. Specify the following file in the Restore Script selection screen.
   /opt/LifeKeeper/samples/GenericARK/Generic_ARK_for_AWS_TransitGateway/tgw_generic_rk.pl
3. Specify the following file in the Remove Script selection screen.
   /opt/LifeKeeper/samples/GenericARK/Generic_ARK_for_AWS_TransitGateway/tgw_generic_rk.pl
4. Specify the following file in the quickCheck Script selection screen.
   /opt/LifeKeeper/samples/GenericARK/Generic_ARK_for_AWS_TransitGateway/tgw_generic_rk.pl
5. Specify the following file in the Local Recovery Script Script selection screen.
   /opt/LifeKeeper/samples/GenericARK/Generic_ARK_for_AWS_TransitGateway/tgw_generic_rk.pl
6. Enter the virtual IP address in the Application Information field.
7. Select Yes for Bring Resource In Service. At this point, the restore script for the resource configuration target program will be executed, and the root table will be set. If you respond No here, extending to other nodes will not occur. In that case, you will need to perform an extend to other nodes later.
8. Specify the resource tag name for the Root Tag. Set any name you prefer.
9. Click Create Instance to create the resource. Then, extend it to the appropriate nodes.

Creating a Dependency

Create a dependency so that the Generic ARK for AWS Transit Gateway resource created in the previous section will be a parent resource, and the IP resource will be a child resource.
To set a dependency, select the Create Dependency menu from the GUI management screen. For specific steps on creating dependencies, refer to Creating a Resource Dependency.
Also, create a dependency with the application resource.

Verifying Configuration

To verify that the configuration was done correctly, perform a switchover for the created resource hierarchy in both directions. In each state, check that clients can connect to the active node using the virtual IP and that no error or warning logs are output.