> 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/how-to-guides/configure-ecs-loadbalancer.md).

# Configure an ECS load balancer

Configure an AWS Classic Load Balancer for accessing Prisma Cloud Console. Console serves its UI and API over HTTPS on port 8083, and Defender communicates with Console over a websocket on port 8084. You’ll set up a single load balancer to forward requests for both port 8083 and 8084 to Console, with the load balancer checking Console’s health using the */api/v1/\_ping* endpoint on port 8083.

For the complete install procedure for Prisma Cloud on Amazon ECS, see [here](https://docs.twistlock.com/docs/latest/install/install_amazon_ecs.html).

1. Log into the AWS Management Console.
2. Go to **Services > Compute > EC2**.
3. In the left menu, go to **Load Balancing > Load Balancers**.
4. Create a load balancer.
   1. Click **Create Load Balancer**.
   2. In **Classic Load Balancer**, click **Create**.
   3. Give your load balancer a name, such as **pc-ecs-lb**.
   4. Leave default **VPC**.
   5. Create the following listener configuration:
      * **Load Balancer Protocol**: TCP
      * **Load Balancer Port**: 8083
      * **Instance Protocol**: TCP
      * **Instance Port**: 8083
   6. Click **Add** to add another listener using following listener configuration:
      * **Load Balancer Protocol**: TCP
      * **Load Balancer Port**: 8084
      * **Instance Protocol**: TCP
      * **Instance Port**: 8084
   7. Click **Next: Assign Security Groups**.
      * Select the **pc-security-group**
   8. Click **Next Configure Security Settings**.
      * Ignore the warning and click **Next: Configure Health Check**
   9. Use the following health check configuration:
      * **Ping Protocol**: HTTPS
      * **Ping Port**: 8083
      * **Ping Path**: /api/v1/\_ping
      * For **Advanced Details**, accept the default settings.
   10. Click **Next: Add EC2 Instances**
       * Do not select any instances.
   11. Click **Next: Add Tags**.
       * Under **Key**, enter **Name**.
       * Under **Value**, enter **pc-ecs-lb**.
   12. Click **Review and Create**.
   13. Review your settings and select **Create**.
   14. Review the load balancer that was created and record its **DNS Name**.


---

# 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/how-to-guides/configure-ecs-loadbalancer.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.