Creating a Kognitio Launcher

The Kognitio Launcher is a web based GUI running on an EC2 instance that is created as part of an AWS CloudFormation Stack that is created from an AWS CloudFormation template.

The launcher allows you to create, monitor, maintain and delete Kognitio servers.

Prerequisites

Before you create a Kognitio Launcher on AWS, you’ll need an AWS account with permission to launch CloudFormation templates.

If you do not have these permissions then contact your AWS administrator and ask them to set up the Kognitio Launcher on your behalf.

Stack Creation

As you create the CloudFormation stack you will need to enter some information about your AWS setup and how you would like the launcher to work and the next section describes these options.

There will be no costs incurred until you actually create a Kognitio Launcher CloudFormation stack where there will be an AWS charge for the EC2 instance the Launcher runs on (you will be asked to confirm that you understand this before the stack is created). When you Launch a Kognitio server cluster using the Launcher you will also be charged for the AWS EC2 instance and for the Kognitio software. You will be provided with a cost estimate and will be asked to confirm you understand the charges before any are incurred.

The typical price per hour on the marketplace pages is for an r4.16xlarge EC2 instance which is a good starting size for asessing Kognitio’s performance but if you want to perform basic functional testing you can specify a smaller instance size when you Launch the Kognitio cluster. Conversely you can launch a cluster containing multiple large EC2 instances for massive performance. The Launcher GUI will also advise on suitable instances for your application.

Start the stack creation process by opening the AWS Marketplace web page and performing the following steps.

  • Read the product overview to confirm that it is what you want and click “Continue to Subscribe” to go to the Subscription page.
  • If have not already subscribed, you will need to click the “Accept Terms” and there will be a wait of a few minutes while the subscription is processed by AWS. Click the “Continue to Configuration” button to continue.
  • On the Configuration page, you need to choose a fulfillment option. You have a choice of creating the Launcher (and the Kognitio server clusters you launch) in an existing VPC or in a new one. If in doubt, choose to create it in a new VPC which the CloudFormation template will create for you. Once you have chosen, you will be asked to choose the software version (the most recent) and the region you want the Stack created in. Note, the instance size shown is just a default and will be chosen later. Click the “Continue to Launch” button to continue.
  • On the Launch page you need to choose the launch action which will normally be “Launch CloudFormation”. Click the “Launch” button to go to the Create Stack page.
  • The Create Stack page will be filled out with the correct defaults and you just need to click “Next” to begin to fill in the stack details.

Stack Details

Choose the VPC option you chose above to see the relevant details.

In a new VPC

You will be prompted for the following details:

Example of Specify Details page for Kognitio Launcher
  • Stack name - enter the name that will be used to identify the Cloud Formation stack that is being created.
  • AdminIpRange - this the IP range used to access the launcher and must be in CIDR format. For simple deployments you can use your current public IP address followed by /32. This restricts access to the Kognitio Launcher to your IP address only. For a more detailed explanation see AWS Launcher Networking.
  • AvailabiltityZone - select an availability zone from the dropdown list. The list will only contain zones for the region you are deploying the launcher in.
  • ClientIpRange - this is the IP range you can access your launched clusters from using ODBC or JDBC for SQL access and SSH for server administration. The IP range must be in CIDR format and for simple deployments you can use your current public IP address followed by /32. This restricts access to any Kognitio clusters you launch to your IP address only. For a more detailed explanation see AWS Launcher Networking.
  • Instance Type - the default t2.large is more than adequate for running the Kognitio Launcher but if you want to be able to create a server on the launcher instance you can specify a larger instance type (16GB of memory and 2 CPUs or more is recommended).
  • KeyName - select the AWS EC2 Key Pair to use for SSH access to the ec2-user on the Kognitio Launcher instance and on EC2 instances created by the launcher. SSH access to the instance can be useful if you have forgotten your launcher password or you need to access the Kognitio service accounts for a Kognitio server.
  • LauncherPassword - enter a password for the Kognitio Launcher. You will need to enter this password when logging into the launchers web interface as the “admin” user.

In an existing VPC

You will be prompted for the following details:

Example of Specify Details page for Kognitio Launcher
  • Stack name - enter the name that will be used to identify the Cloud Formation stack that is being created.
  • AdminIpRange - this the IP range used to access the launcher and must be in CIDR format. For simple deployments you can use your current public IP address followed by /32. This restricts access to the Kognitio Launcher to your IP address only. For access by other nodes within the VPC you can use the VPC CIDR. For a more detailed explanation see AWS Launcher Networking.
  • ClientIpRange - this is the IP range you can access your launched clusters from using ODBC or JDBC for SQL access and SSH for server administration. The IP range must be in CIDR format and for simple deployments you can use your current public IP address followed by /32. This restricts access to any Kognitio clusters you launch to your IP address only. For access by other nodes within the VPC you can use the VPC CIDR. For a more detailed explanation see AWS Launcher Networking.
  • Instance Type - the default t2.large is more than adequate for running the Kognitio Launcher but if you want to be able to create a server on the launcher instance you can specify a larger instance type (16GB of memory and 2 CPUs or more is recommended).
  • KeyName - select the AWS EC2 Key Pair to use for SSH access to the ec2-user on the Kognitio Launcher instance and on EC2 instances created by the launcher. SSH access to the instance can be useful if you have forgotten your launcher password or you need to access the Kognitio service accounts for a Kognitio server.
  • LauncherPassword - enter a password for the Kognitio Launcher. You will need to enter this password when logging into the launchers web interface as the “admin” user.
  • VPC - select the existing VPC you want the Kognitio Launcher (and the Launched Kognitio server clusters) to be placed in.
  • VPCSubnet - select the subnet of the selected VPC to place the Kognitio Launcher in. Note: You need to make sure the subnet you choose is part of the VPC you chose above.

Once the Stack name and other parameters are complete select “Next”.

Options

The settings on this page are all optional.

  • Tags - Tags set here are applied to the launcher instance and all the launched Kognitio server instances. Tags can be useful for tracking costs in your AWS billing dashboard.
  • Permissions - This should normally be left blank but it can be used to set the permissions used during the creation of the CloudFormation stack. Insufficient permissions will cause the stack create to fail.
  • Rollback Triggers - Management of AWS Cloud Formation montioring and rollback via triggers set up prior to deployment. Advanced users only.
  • Advanced - additional options for notification and stack policies etc.

Each option has a link to the appropriate section in the AWS help if more detail is required.

Set options as required or simply click on “Next”.

Review

The final page allows you to review your set-up and look at the estimated cost.

Once you are happy with the details and options you need to tick the checkbox to acknowledge that Creating the stack will create IAM resources. The resources that will be created include; IAM Policies, Roles and Instance Profiles; EC2 Security Groups and an EC2 instance (the launcher).

Tick the checkbox to allow creation of the launcher CloudFormation stack.

Full details of the resources created can be found by examining the CloudFormation template.

Click on the “Create” button to create the stack.

Depending on the size of the instance you have specified, the Kognitio Launcher will be ready in approximately 3 minutes.

To monitor progress, click on the stacks link at the top level of the CloudFormation page, this will show you all the stacks. Refresh this page occasionally and when all steps are complete, the status of the Kognitio launcher stack will change from “CREATE_IN_PROGRESS” to “CREATE_COMPLETE”.

You will then be able to access the Kognitio Launcher via its PublicURL (or PrivateURL in the case of an existing VPC stack) which you can navigate to by:

  • Clicking on your Stack Name
  • Expanding the Outputs section directly below the stack details
  • Clicking on the PublicURL or PrivateURL link

For more information see AWS Launcher Networking.

You will see a warning in the browser, this is due to the https certificate being self signed and it is safe to ignore this warning and continue. You will now see the login form; leave the user as admin and enter the LauncherPassword you specified in the details section to login to the launcher.

You are now ready to launch a Kognitio on AWS cluster.