> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/33/install/deploy-console/console-on-eks.md).

# Deploy the Prisma Cloud Console on EKS

[Amazon Kubernetes Service (EKS)](https://aws.amazon.com/eks/#) lets you deploy Kubernetes clusters on demand. Use our standard Kubernetes install method to deploy Prisma Cloud to EKS.

If using Bottlerocket OS-based nodes for your EKS Cluster:

* Pass the `--container-runtime containerd` flag to `twistcli`.
* Or select the **Container Runtime type** as `containerd` in the Console UI when generating the Defender `YAML` or `Helm` chart.

Follow the instructions to [deploy Defenders as DaemonSet](/admin-guide/33/install/deploy-defender/orchestrator/install-kubernetes-cri.md) for more details.

**Prerequisites**

* You have deployed an Amazon EKS cluster.
* You have [downloaded the Prisma Cloud software](/admin-guide/33/tools/twistcli.md).

1. Generate the Prisma Cloud Compute Console deployment file.

   ```
   $ twistcli console export kubernetes \
     --service-type LoadBalancer \
     --storage-class gp2
   ```
2. Deploy Console.

   ```
   $ kubectl create -f twistlock_console.yaml
   ```
3. Wait for the service to come up completely.

   ```
   $ kubectl get service -w -n twistlock
   ```
4. Continue with the rest of the [installation for Kubernetes clusters](/admin-guide/33/install/deploy-console/console-on-kubernetes.md).


---

# 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.prismacloud.io/admin-guide/33/install/deploy-console/console-on-eks.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.