Configuring the First KeyControl Node

You need to configure the KeyControl instance using SSH before you can use the KeyControl webGUI to configure and maintain your KeyControl cluster.

The following procedure describes how to configure the first KeyControl node in the cluster. If you are adding this node to an existing cluster, see Configuring Additional KeyControl Nodes.

Before You Begin 

Make sure you have the following information:

• The Amazon instance ID for the KeyControl instance.
• The Elastic (Public) IP address associated with the instance.
• The private key file (in pem format) that was used when the instance was created.

Tip:

To find this information, select Instances from the Amazon Management Console EC2 Dashboard, then select the KeyControl instance in the table. In the Description tab, look at the Instance ID, IPv4 Public IP, and Key pair name fields.

Procedure 

1. Open a terminal window and navigate to the directory in which you have stored the private key file. If you have not used this key file before, make sure the permissions are set to -r-------- (chmod 400).

2. Log into the sysmenus account on the KeyControl instance using the private key file.

   ssh -i <key-file>.pem sysmenus@<Elastic-IP-addy>

   where key-file.pem is the name of the key pair associated with the instance and Elastic-IP-Addy is the public IPv4 address associated with the instance. For example, if your key pair is called KeyControl-Cluster-NorthAmerica.pem and the Elastic IP address is 52.18.58.35, you would enter:

   ssh -i KeyControl-Cluster-NorthAmerica.pem sysmenus@52.18.58.35

3. When prompted for the sysmenus password, enter the Amazon instance ID for the KeyControl instance that you are configuring.

4. On the Set System Password screen, enter a password for the KeyControl system administration account root and press Enter. The password must contain at least 6 characters and cannot contain spaces or any non-ASCII characters.

   This password cannot be reset from within KeyControl. If you lose the password, you will need to re-install the KeyControl software.

   Note:

   This password controls access to the System Console Menu that allows users to perform some KeyControl administration tasks. It does not permit a KeyControl user to access the full OS.

5. When prompted about whether you want to add this node to an existing cluster, select No and press Enter.
6. Review the confirmation dialog that provides the public URLs that can be used with the KeyControl webGUI as well as the private IP address that you can use if you want to add other KeyControl nodes to this cluster. When you are done, press Enter to finish the installation and view the main System Console Menu.

What to Do Next 

Set up the KeyControl webGUI as described in Initializing the KeyControl webGUI.