> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/get-started/connect-your-environment/source-code/self-hosted-analysis/deployment-paths.md).

# Deployment Paths

Choose your deployment path based on your existing infrastructure

Konvu Self-Hosted Analysis can be deployed on any Kubernetes cluster. Choose your path:

## Path 1: I Have a Kubernetes Cluster

**Use this if:** You already have Kubernetes running (AWS EKS, Google GKE, Azure AKS, on-premises, etc.)

**What you'll do:**

1. Create secrets manually with kubectl or inline in Helm values
2. Deploy controller and broker via Helm charts
3. Verify deployment

**Time estimate**: \~15 minutes

**Requirements**:

* Kubernetes v1.28+
* kubectl access
* Helm 3.12+
* Internet egress to `sensors.konvu.com` and GitHub

**Next step**: Continue to [Installing the Broker and Controller](/konvu/get-started/connect-your-environment/source-code/self-hosted-analysis/installing-the-broker-and-controller.md)

***

## Path 2: I Need AWS Infrastructure

**Use this if:** You want to provision a complete AWS EKS cluster with infrastructure as code

**What you'll do:**

1. Store credentials in AWS Secrets Manager
2. Use Terraform/OpenTofu to provision:
   * VPC and networking
   * EKS cluster (Kubernetes v1.34)
   * Karpenter for autoscaling
   * External Secrets Operator for secret sync
   * IAM roles (IRSA)
3. Deploy controller and broker via Helm (automated by Terraform)

**Time estimate**: \~20 minutes

**Requirements**:

* AWS account with appropriate permissions
* Terraform/OpenTofu
* AWS CLI

**Next step**: Continue to [Setting Up AWS Infrastructure](/konvu/get-started/connect-your-environment/source-code/self-hosted-analysis/setting-up-infrastructure.md)

***

## Comparison

| Feature                         | Path 1: Existing Cluster           | Path 2: AWS Provisioning                        |
| ------------------------------- | ---------------------------------- | ----------------------------------------------- |
| **Kubernetes distribution**     | Any (EKS, GKE, AKS, on-prem, etc.) | AWS EKS only                                    |
| **Secret management**           | Manual kubectl or inline in Helm   | AWS Secrets Manager + External Secrets Operator |
| **Infrastructure provisioning** | You manage                         | Terraform provisions everything                 |
| **Autoscaling**                 | Your choice                        | Karpenter included                              |
| **Deployment method**           | Helm only                          | Terraform + Helm                                |
| **Complexity**                  | Lower                              | Higher                                          |
| **Flexibility**                 | Works anywhere                     | AWS-specific                                    |

Both paths result in the same running application. Choose based on your infrastructure needs and existing setup.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.konvu.com/konvu/get-started/connect-your-environment/source-code/self-hosted-analysis/deployment-paths.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.