Install and configure the Snyk Broker client
Snyk’s recommended and supported method of running the Snyk Broker client is using Docker.
To install and configure your client:
  1. 1.
    Visit the broker repository and follow the instructions for the relevant integration to run one of our provided images, or derive your own.
    1. 1.
      There are some examples available at Snyk Broker set-up examples
  2. 2.
    For the environment variables required to run the Broker client, you must:
    1. 2.
      Ensure that you have the necessary permissions granted to your API credentials for the integration you are using by following one of our integration guides.
  3. 3.
    After the broker is running, identifying Broker server appears towards the end of the log results, showing that a connection to Snyk has been established
  4. 4.
    Visit the settings for your brokered integration in the Snyk application to see a message like the following:
The base set-up for SCMs will enable usage of Snyk Open Source and scan of Dockerfiles. To get the full platform set up through the broker, please follow:

Snyk Broker Helm Chart

Alternatively, if you are using Kubernetes and would like to deploy the broker through a Helm chart, please use the provided Snyk Broker Helm Chart

Advanced Configuration

The Broker client runs an HTTP server by default. It can be configured to run an HTTPS server for local connections. This requires an SSL certificate and a private key to be provided to the docker container at runtime.
For example, if your certificate files are found locally at ./private/broker.crt and ./private/broker.key, provide these files to the docker container by mounting the folder and using the HTTPS_CERT and HTTPS_KEY environment variables:
docker run --restart=always \
-p 8000:8000 \
-e BROKER_TOKEN=secret-broker-token \
-e GITHUB_TOKEN=secret-github-token \
-e PORT=8000 \
-e HTTPS_CERT=/private/broker.crt \
-e HTTPS_KEY=/private/broker.key \
-v /local/path/to/private:/private \
Note that BROKER_CLIENT_URL now has the HTTPS scheme.
Git with an internal certificate
By default, the Broker client establishes HTTPS connections to the Git. If your Git is serving an internal certificate (signed by your own CA), you can provide the CA certificate to the Broker client.
For example, if your CA certificate is at ./private/ca.cert.pem, provide it to the docker container by mounting the folder and using the CA_CERT environment variable:
docker run --restart=always \
-p 8000:8000 \
-e BROKER_TOKEN=secret-broker-token \
-e \
-e \
-e PORT=8000 \
-e CA_CERT=/private/ca.cert.pem \
-v /local/path/to/private:/private \

Proxy support

Proxy configuration, see Configure Docker to use a proxy server
-e HTTP_PROXY=http://my.proxy.address:8080
-e HTTPS_PROXY=http://my.proxy.address:8080
-e NO_PROXY=*,,

Disable certificate verification

To disable certificate verification, e.g., in the case of self-signed certificates, add to the docker run command:

Custom approved-listing filter

The default approved-listing filter supports the bare minimum to operate on all repositories supported by Snyk. In order to customize the approved-listing filter, create the default one locally by installing snyk-broker and running broker init [Git type]. The created accept.json is the default filter for the chosen Git. Place the file in a separate folder such as ./private/accept.json, and provide it to the docker container by mounting the folder and using the ACCEPT environment variable:
docker run --restart=always \
-p 8000:8000 \
-e BROKER_TOKEN=secret-broker-token \
-e GITHUB_TOKEN=secret-github-token \
-e PORT=8000 \
-e ACCEPT=/private/accept.json
-v /local/path/to/private:/private \
Types of Filtering
By Header
Add a validation block with the following key/values:
Value Type
The name of the header you wish to filter on. If this is defined then the named header must explicitly exist on the request otherwise it will be blocked
The header value must match one of the defined strings
For example, to only allow the SHA Media Type accept header for requests to the GitHub Commits API you would add the following:
"method": "GET",
"path": "/repos/:name/:repo/commits/:ref",
"origin": "https://${GITHUB_TOKEN}@${GITHUB_API}",
"valid": [
"header": "accept",
"values": ["application/vnd.github.v4.sha"]
Example of custom approved-listing filters for each SCM: Snyk Broker set-up examples and the more generic list in

Upgrade your Snyk Broker client

Snyk regularly updates the Broker client in order to provide new features, bug fixes and more. Our full list of versions and their release notes are available from GitHub as part of our Broker project. We also encourage you to subscribe to the RSS feed for that page to easily receive info about versions as they are released.
When upgrading your broker there may be some new rules added that Snyk requires to function correctly. Therefore, you will need to re-initialize your API allow-list. If you added or removed any rules to customize your allow-list (for example, to support files greater in size than 1Mb), you will need to re-apply these changes to the new allow-list.