IP Restriction

Restrict access to a Service or a Route by either whitelisting or blacklisting IP addresses. Single IPs, multiple IPs or ranges in CIDR notation like 10.10.10.0/24 can be used.

Terminology

• plugin: a plugin executing actions inside Kong before or after a request has been proxied to the upstream API.
• Service: the Kong entity representing an external upstream API or microservice.
• Route: the Kong entity representing a way to map downstream requests to upstream services.
• Consumer: the Kong entity representing a developer or machine using the API. When using Kong, a Consumer only communicates with Kong which proxies every call to the said upstream API.
• Credential: a unique string associated with a Consumer, also referred to as an API key.
• upstream service: this refers to your own API/service sitting behind Kong, to which client requests are forwarded.

Configuration

This plugin is compatible with requests with the following protocols:

• http
• https

This plugin is compatible with DB-less mode.

Enabling the plugin on a Service

With a database

Configure this plugin on a Service by making the following request:

$ curl -X POST http://kong:8001/services/{service}/plugins \
    --data "name=ip-restriction"  \
    --data "config.whitelist=54.13.21.1" \
    --data "config.whitelist=143.1.0.0/24"

Without a database

Configure this plugin on a Service by adding this section do your declarative configuration file:

plugins:
- name: ip-restriction
  service: {service}
  config: 
    whitelist:
    - 54.13.21.1
    - 143.1.0.0/24

In both cases, {service} is the id or name of the Service that this plugin configuration will target.

Enabling the plugin on a Route

With a database

Configure this plugin on a Route with:

$ curl -X POST http://kong:8001/routes/{route}/plugins \
    --data "name=ip-restriction"  \
    --data "config.whitelist=54.13.21.1" \
    --data "config.whitelist=143.1.0.0/24"

Without a database

Configure this plugin on a Route by adding this section do your declarative configuration file:

plugins:
- name: ip-restriction
  route: {route}
  config: 
    whitelist:
    - 54.13.21.1
    - 143.1.0.0/24

In both cases, {route} is the id or name of the Route that this plugin configuration will target.

Enabling the plugin on a Consumer

With a database

You can use the http://localhost:8001/plugins endpoint to enable this plugin on specific Consumers:

$ curl -X POST http://kong:8001/consumers/{consumer}/plugins \
    --data "name=ip-restriction" \
     \
    --data "config.whitelist=54.13.21.1" \
    --data "config.whitelist=143.1.0.0/24"

Without a database

Configure this plugin on a Consumer by adding this section do your declarative configuration file:

plugins:
- name: ip-restriction
  consumer: {consumer}
  config: 
    whitelist:
    - 54.13.21.1
    - 143.1.0.0/24

In both cases, {consumer} is the id or username of the Consumer that this plugin configuration will target.

You can combine consumer_id and service_id

in the same request, to furthermore narrow the scope of the plugin.

Global plugins

• Using a database, all plugins can be configured using the http://kong:8001/plugins/ endpoint.
• Without a database, all plugins can be configured via the plugins: entry on the declarative configuration file.

A plugin which is not associated to any Service, Route or Consumer (or API, if you are using an older version of Kong) is considered "global", and will be run on every request. Read the Plugin Reference and the Plugin Precedence sections for more information.

Parameters

Here's a list of all the parameters which can be used in this plugin's configuration:

Note that the whitelist and blacklist models are mutually exclusive in their usage, as they provide complimentary approaches. That is, you cannot configure the plugin with both whitelist and blacklist configurations. An whitelist provides a positive security model, in which the configured CIDR ranges are allowed access to the resource, and all others are inherently rejected. By contrast, a blacklist configuration provides a negative security model, in which certain CIDRS are explicitly denied access to the resource (and all others are inherently allowed).