Create a Kublr platform


The Kublr Demo/Installer must be installed. If you haven’t done that yet, please refer to the Installation Guide for the Kublr Demo/Installer.

To deploy a cluster in your AWS account with Kublr, you’ll need to create an AWS policy and an AWS API Access Key. Please refer to Register AWS Policy, create User and Create API Credentials.


This document describes the steps necessary to deploy the Kublr Platform in an Amazon Web Services infrastructure. It contains the following steps:

  1. Deploy Kublr Platform to AWS infrastructure.
  2. Open deployed Kublr Platform.
  3. (Optional) Setup custom DNS name for Kublr Platform.

Connect AWS and Kublr

Procedure is the same as for creating an AWS k8s cluster.

Deploying Kublr Platform to AWS infrastructure

Fully functional Kublr Platform includes all Kublr features (IAM, RBAC, centralized Logging/Monitoring and etc). Suitable for building you own Kubernetes cluster management platform.

See some platform parameters description here.

To add a new platform:

  1. On the left menu, click Clusters.
  2. Click Add Cluster. Add New Cluster The Select Installation Type dialog is displayed.
  3. In the Select Installation Type dialog, click Platform.
  4. Click Continue Setup. Installation Type - Platform The DEPLOY FULL KUBLR PLATFORM dialog is displayed.
  5. In the dialog, in the upper (Planning) section, set general parameters of your platform as described below.
  6. Set Provider to “Amazon Web Services”.
  7. From the Credentials list, select previously created AWS credentials.

    If credentials were not created previously, use Add New Credentials.

  8. Specify Cluster Name.

  9. Set:

    • Region
    • Kubernetes Version AWS-Add Platform-General Settings
  10. If necessary, expand the Advanced Options and set them.

  11. Scroll to the Master Configuration section.

  12. Specify the parameters of the master node(s) of your platform as described below.

  13. Select Instance Type from the list.

  14. From the Masters list, select the number of master or management nodes in correspondence with the selected Instance Type.

  15. From the Operating System list, select the host OS for virtual machines in the platform. AWS-Add Platform-Master Configuration

  16. Optionally, select Public SSH Key from the list.

  17. If necessary, expand the Advanced Options and set them.

  18. Scroll to the Instance Group section (default name group1).

  19. Specify the parameters of the work node(s) in your group as described below.

  20. Select Instance Type from the list.

  21. To select the number of work nodes in a group, do one of the following:

    • In the Nodes field, set the number of work nodes.
    • Select the Auto-Scaling option, and then set the Min Nodes and Max Nodes limitations.
  22. From the Operating System list, select the host OS for virtual machines in the cluster.

  23. If necessary, set your own name for the instance group.

    Note You can also clone or delete the current instance group, or add another one. Instance Group-Operations

  24. If necessary, expand the Advanced Options and set them.

  25. Scroll to the Features section.

  26. In the Control Plane sub-section:

  27. Specify password for accessing the platform.

  28. In the Centralized Logging sub-section:

  29. In Master Nodes, specify the number of master nodes for ElasticSearch cluster.

  30. Set:

    • Number of Data nodes
    • Number of Client nodes
  31. If necessary, select or clear the Persistence enabled option.

    If selected, set Disk size.

  32. If necessary, select the Add AWS CloudWatch Logs option.

  33. In the Centralized Monitoring sub-section:

  34. For Prometheus, select or clear the Persistence enabled option. If selected, set Disk size.

  35. For Grafana, select or clear the Persistence enabled option. If selected, set Disk size.

  36. In the Ingress Controller sub-section:

  37. Enable or disable NGINX Ingress Controller.

  38. If necessary, select Use Let’s Encrypt.

    If selected, set Email and ACME API Endpoint. AWS-Add Platform-Features Configuration

  39. At the bottom of the DEPLOY FULL KUBLR PLATFORM dialog, click Confirm and Install.

    A notification is displayed “Your cluster is being created. It might take a few minutes.”.

  40. In the notification window, click OK.

    Your new platform page is displayed on the Events tab showing the platform creation progress. AWS-Add Platform-Creation Progress

Opening deployed Kublr Platform

The Kublr Platform creation may take up to 30 minutes to complete.

  1. Once it’s done, on the Clusters page you will see: Kublr Platform
  2. Click on “Open Kublr Platform” button to open the Kublr platform.
  3. Please allow it to use self-signed SSL certificate. SSL Certificate error
  4. Sign in to the Kublr Platform using the admin Username and Password provided while creating Kublr Platform above.

Now you can use Kublr Platform!

(Optional) Setting up custom DNS name for the Kublr Platform

This optional step is required if you want a user-friendly DNS name such as instead of the default loadbalancer address, which looks like “”.

To do this, please create a new DNS A record with type Alias for pointing to LoadBalancer DNS Name.

Instructions on how to setup SSL certificate for this domain are provided in the article: Ingress TLS/SSL Setup.