KEMP 360 Central is a centralized management, orchestration, and monitoring application that enables the administration of deployed LoadMaster instances.
KEMP 360 Central can be used to perform administrative tasks on each LoadMaster instance. This provides ease of administration because multiple LoadMasters can be administered in one place, rather than accessing each LoadMaster individually.
The purpose of this document is to provide step-by-step instructions on deploying KEMP 360 Central in Amazon Web Services (AWS).
This document is for anyone who needs more information about deploying KEMP 360 Central within AWS.
To support KEMP 360 Central for AWS, the following are required:
An active subscription to Amazon Web Services (AWS) Virtual Machines
A client computer running Windows 7 or higher
Internet Explorer 11 or higher
A Virtual Private Cloud (VPC) set up and configured in AWS
Valid AWS credentials
AWS Command Line Interface (CLI) must be installed
When starting a new instance, you will be prompted to select a key pair. A key pair is a certificate and key. It is used to SSH to the KEMP 360 Central instance. Keep the downloaded key in a safe place. Steps on how to add a key pair are below:
1. Log in to the AWS console.
2. Click EC2.
3. In the main menu, select Key Pairs.
4. Click Create Key Pair.
5. Enter a name for the key pair and click Yes. The .pem file downloads.
As this file is required to SSH into the KEMP 360 Central instance, make a note of where this file is stored. This file needs to reside on the client that is used to SSH to KEMP 360 Central.
If you are using a client that does not accept PEM format, you will need to convert the file to another format, for example PPK for Putty.
6. If you are using Linux, change the permissions of the key pair file so it can work. To do this, go to the directory where the file is stored and run the following command:
chmod 600 <FileName>
To start an instance, follow the steps below:
1. Access the AWS home page.
2. Click the Sign In to the Console button.
3. Log in using your account details.
5. Click EC2.
6. Click Instances.
7. Click Launch Instance.
8. Select AWS Marketplace.
9. Click Select for the relevant version to be deployed.
a) Select the appropriate instance type.
b) Click Next: Configure Instance Details.
10. Ensure you select the correct item (Virtual Private Cloud) in the Network drop-down list.
11. Ensure that the Auto-assign Public IP option is set to Enable.
12. Configure any other setting as needed.
13. Click Review and Launch.
a) Before launching, click Edit security groups.
b) Select the Security Group of your choosing or create a new security group.
The following rules are needed in the security group:
Custom TCP Rule with the Port Range 443 for the WUI
SSH for the SSH management interface with the Port Range 22
Any additional rules that are needed for other ports for services that will be set up, for example Remote Desktop Protocol (RDP) if load balancing Windows RDP servers, or HTTPS for a secure website
c) Select the relevant source option from the drop-down list and enter custom IP addresses as needed.
Management interfaces should only be allowed using trusted IP addresses. You should also add rules for any services you intend on creating. You can always revisit this security group later if additional services become necessary.
d) Click Review and Launch.
e) Click Launch.
f) Select the appropriate key pair for your environment. This is the key pair that was created in the Create a New Key Pair section. Use this key pair or another one that you might have. This key pair is needed to connect using SSH.
g) Select the check box.
h) Click Launch Instances.
i) Click View Instances. The Public IP address or Domain Name System (DNS) address can be used to connect to the instance using HTTPS on port 443.
After your instance state is Running, you can connect to your KEMP 360 Central instance. For more information on this, including instructions on how to license KEMP 360 Central, refer to the KEMP 360 Central Feature Description on the KEMP Documentation Page.
Related documents are listed below:
This document was last updated on 20 July 2018.