Deckhouse Platform in Amazon AWS

Congratulations, your Deckhouse platform is up and running!

Now that you have installed and properly configured Deckhouse, let’s look at what you can do with it.

By default, the Dex is used for accessing all the components.

Here are credentials generated in the previous steps:

  • Username —

Use them to access the web interface of the Deckhouse components.


Up-to-date Deckhouse documentation in your cluster

The in-cluster documentation for a specific version of Deckhouse used in your cluster is available at


Explore Grafana dashboards bundled with Deckhouse at

Go to to access Prometheus directly.

Learn more about the monitoring module.


The Kubernetes Dashboard is available at:

Status page

Visit to get information about the overall status of Deckhouse and its components.

The page provides detailed SLA statistics for each component and time frame.

Deploying your first application

Setting up a CI/CD system

Create a ServiceAccount to use for deploying to the cluster and grant it all the necessary privileges.

You can use the generated kubeconfig file in Kubernetes with any deployment system.

Routing traffic

Create a Service and Ingress for your application.

Learn more about the capabilities of the ingress-nginx module.

Monitoring your application

Add "my-app" and "80" annotations to the Service created.

For more information, see the monitoring-custom module’s documentation.

Other features

Managing nodes

Run the following command to list nodegroups created in the cluster during the deployment process: kubectl get nodegroups. For more information, see the node-manager’s documentation.

You only need to make changes to minPerZone and maxPerZone parameters to scale the existing groups. If these two parameters are not equal, Deckhouse will automatically launch an autoscaler.

You need to create a new InstanceClass and a NodeGroup referring to it to create new groups.

External authentication

Deckhouse supports various external authentication mechanisms.

Configuring DexProvider

You have to configure a DexProvider object to enable, e.g., GitHub-based authentication. After creating the DexProvider object, all access attempts to Deckhouse components such as Grafana, Dashboard, etc., will be authenticated using GitHub.

External authentication for any Ingress

You have to create a DexAuthenticator object to enable external authentication for any Ingress resource.

External authentication for the Kubernetes API

Configure publishAPI, download kubectl and create a kubeconfig file for external access to the API using the web interface available at

What’s next?

Detailed information about the system and the Deckhouse Platform components is available in the documentation.

Please, reach us via our online community if you have any questions.