> For the complete documentation index, see [llms.txt](https://docs.amesa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amesa.com/training-infrastructure/connecting-a-cluster.md).

# Connecting a Cluster

## Introduction

This page covers manually installing the AMESA components onto the cluster.

## Requirements

To install AMESA on your cluster, you'll need access to the [AMESA No-Code UI](https://app.amesa.com) and a valid license key.

Additionally, to run the installation script, you need to have Kubectl set up with access to the cluster.

## Steps

1. Log in to the No-Code app
2. Navigate to the Clusters page
3. Click "Create"

<figure><img src="/files/vc7umHni8y1bLlnVxNGD" alt=""><figcaption></figcaption></figure>

1. In the pop-up, choose a display name for your cluster

<figure><img src="/files/8GYz8GKTczBYyEzmh5qB" alt=""><figcaption></figcaption></figure>

1. Select the cloud vendor you're using, or "custom" if none.
2. Copy the command
3. Run the command in your terminal where you have access to a kubectl
4. When the command exits without errors, the installation was complete.
5. Refresh the clusters page. Your custom cluster should now say "Connected" and list its specifications.

You can now select the cluster from the dropdown menu when training.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.amesa.com/training-infrastructure/connecting-a-cluster.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.