---
title: "Apply your Meko license"
url: "https://docs.mekodata.ai/byoc/prerequisites/meko-license/"
---

# Apply your Meko license

Apply the license file from Meko support to your EKS cluster

Meko support gives you a license file for your environment. It holds the credentials that let your cluster pull the Meko charts and images from Quay, and that let the collectors ship metrics and logs. You apply it to the cluster before you deploy, in the namespace that Meko will be installed into.

The license is a Kubernetes manifest of three Secrets:

| Secret                | Holds                                                                                                                                    |
|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------|
| `quay-registry-creds` | The Quay robot credentials, as a `dockerconfigjson`. Every Meko pod pulls its image with it, and the install uses it to pull the charts. |
| `byoc-metrics-auth`   | The password for the metrics pipeline (`password`)                                                                                       |
| `datadog-api`         | The key for the log pipeline (`api-key`)                                                                                                 |

Before it creates anything, the install checks that all three are in the namespace, each with its key, and stops if one is missing. It never replaces them.

## Choose the namespace

The Meko console's install command starts with a header, and its first value, `NS`, is the namespace the deployment uses. It defaults to the name of your environment, or to `meko` if that name can't be used as a namespace. Keep that value, or change it now. Whatever you choose, the license and the install command must use the same namespace.

## Apply the license

The install checks for the license before it creates anything, so create the namespace yourself and apply the license into it:

```sh
export NS=<namespace>          # the NS value in the install command
kubectl create namespace "$NS" --dry-run=client -o yaml | kubectl apply -f -
kubectl apply -n "$NS" -f <license file>
```

The first command is safe to run when the namespace already exists.

If you later change `NS` in the install command, apply the license again in the new namespace. Keep the file. You also apply it again if Meko support issues you a new one.

## Next

[Deploy Meko on AWS](/byoc/deploy-aws/).
