> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/platform-administration/snyk-broker/universal-broker/preparing-for-creating-universal-broker-deployments.md).

# Preparing for creating Universal Broker deployments

Before creating deployments, ensure you have met the [prerequisites](/platform-administration/snyk-broker/universal-broker/prerequisites-for-universal-broker.md).

## Prepare hosts for the installation of Universal Broker

Snyk recommends configuring at least two separate instances of the Broker Client for each integration, either on different hosts or installed using Kubernetes. This ensures that you always have at least two instances running for redundancy. To install the Universal Broker using Helm please see the [Snyk Universal Broker Helm Chart](https://github.com/snyk/snyk-universal-broker-helm).

## Configure your network for using Universal Broker

If you use a proxy server, ensure you configure it and any firewalls to allow the Broker Client inbound and outbound access as follows.

Establish the outbound connection on port 443 from the Broker Client running in your environment to `https://broker.snyk.io` and `https://api.snyk.io` or your regional Broker URL.

Establish an internal connection that allows inbound access from the integration (SCM, CR) to the Broker Client at the `BROKER_CLIENT_URL` on the port you have configured (typically 8000). This is not inbound from the internet.

Traffic initiated from the Snyk Broker server side always uses the latest available Broker connection. All activity from the Snyk side, such as traffic driven by recurring tests, appears on only one of your replicas at a time. The amount of Snyk activity is proportional to the activity in the repositories or Jira items. That activity generates webhooks, which are distributed across all replicas.

Use the Universal Broker `snyk-broker-config` CLI tool to configure and manage connections, integrations, and all Universal Broker resources.

## Using a previous installation

If you have not previously installed the Universal Broker, refer to the Prerequisites for Universal Broker and [Basic steps to install and configure Universal Broker.](/platform-administration/snyk-broker/universal-broker/basic-steps-to-install-and-configure-universal-broker.md)

Be sure to set your environment variables to make usage easier, including when you are installing the `snyk-broker-config` CLI tool. Use the following commands:

Linux/Mac

* `export SNYK_TOKEN=<your_snyk_token>`
* `export TENANT_ID=<your_tenant_id>`

Windows

* `set SNYK_TOKEN=<your_snyk_token>`
* `set TENANT_ID=<your_tenant_id>`

If the Universal Broker has already been installed, set the Install ID as an environment variable for easier usage. Use the following commands:

Linux/Mac

* `export INSTALL_ID=<your_install_id>`

Windows

* `set INSTALL_ID=<your_install_id>`


---

# 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.snyk.io/platform-administration/snyk-broker/universal-broker/preparing-for-creating-universal-broker-deployments.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.