Table of Contents
In this section you will find a summary about the recommended network and firewall settings for Kong.
Kong uses multiple connections for different purposes.
- management api
The proxy ports is where Kong receives its incoming traffic. There are two ports with the following defaults;
8000for proxying. This is where Kong listens for HTTP traffic. Be sure to change it to
80once you go to production. See proxy_listen.
8443for proxying HTTPS traffic. Be sure to change it to
443once you go to production. See proxy_listen and the
These are the only ports that should be made available to your clients.
This is the port where Kong exposes its management api. Hence in production this port should be firewalled to protect it from unauthorized access.
8001provides Kong’s Admin API that you can use to operate Kong. See admin_listen.
8444provides the same Kong Admin API but using HTTPS. See admin_listen and the
Below are the recommended firewall settings:
- The upstream Services behind Kong will be available via the proxy_listen interface/port values. Configure these values according to the access level you wish to grant to the upstream Services.
- If you are binding the Admin API to a public-facing interface (via admin_listen), then protect it to only allow trusted clients to access the Admin API. See also Securing the Admin API.
- Your proxy will need have rules added for any TCP Stream listeners that you configure. For example, if you want Kong to manage traffic on port
4242, your firewall will need to be allow traffic on said port.