Skip to content
|
Plugin Hub
github-edit-pageEdit this page
report-issueReport an issue
header icon

Basic config examples for Service Protection

By Kong Inc.

Basic configuration examples

The following examples provide some typical configurations for enabling the service-protection plugin on a service.

Make the following request:

curl -X POST http://localhost:8001/services/{serviceName|Id}/plugins \
    --header "accept: application/json" \
    --header "Content-Type: application/json" \
    --data '
    {
  "name": "service-protection",
  "config": {
    "window_size": [
      30
    ],
    "window_type": "sliding",
    "limit": [
      5
    ],
    "namespace": "example_namespace"
  }
}
    '

Replace SERVICE_NAME|ID with the id or name of the service that this plugin configuration will target.

Make the following request, substituting your own access token, region, control plane ID, and service ID:

curl -X POST \
https://{us|eu}.api.konghq.com/v2/control-planes/{controlPlaneId}/core-entities/services/{serviceId}/plugins \
    --header "accept: application/json" \
    --header "Content-Type: application/json" \
    --header "Authorization: Bearer TOKEN" \
    --data '{"name":"service-protection","config":{"window_size":[30],"window_type":"sliding","limit":[5],"namespace":"example_namespace"}}'

See the Konnect API reference to learn about region-specific URLs and personal access tokens.

First, create a KongPlugin resource:

echo "
apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: service-protection-example
plugin: service-protection
config:
  window_size:
  - 30
  window_type: sliding
  limit:
  - 5
  namespace: example_namespace
" | kubectl apply -f -

Next, apply the KongPlugin resource to an ingress by annotating the service as follows:

kubectl annotate service SERVICE_NAME konghq.com/plugins=service-protection-example

Replace SERVICE_NAME with the name of the service that this plugin configuration will target. You can see your available ingresses by running kubectl get service.

Note: The KongPlugin resource only needs to be defined once and can be applied to any service, consumer, or route in the namespace. If you want the plugin to be available cluster-wide, create the resource as a KongClusterPlugin instead of KongPlugin.

Add this section to your declarative configuration file:

plugins:
- name: service-protection
  service: SERVICE_NAME|ID
  config:
    window_size:
    - 30
    window_type: sliding
    limit:
    - 5
    namespace: example_namespace

Replace SERVICE_NAME|ID with the id or name of the service that this plugin configuration will target.

Prerequisite: Configure your Personal Access Token 
terraform {
  required_providers {
    konnect = {
      source  = "kong/konnect"
    }
  }
}

provider "konnect" {
  personal_access_token = "kpat_YOUR_TOKEN"
  server_url            = "https://us.api.konghq.com/"
}

Add the following to your Terraform configuration to create a Konnect Gateway Plugin:

resource "konnect_gateway_plugin_service_protection" "my_service_protection" {
  enabled = true

  config = {
    window_size = [30]
    window_type = "sliding"
    limit = [5]
    namespace = "example_namespace"
  }

  control_plane_id = konnect_gateway_control_plane.my_konnect_cp.id
  service = {
    id = konnect_gateway_service.my_service.id
  }
}

A plugin which is not associated to any service, route, consumer, or consumer group is considered global, and will be run on every request.

  • In self-managed Kong Gateway Enterprise, the plugin applies to every entity in a given workspace.
  • In self-managed Kong Gateway (OSS), the plugin applies to your entire environment.
  • In Konnect, the plugin applies to every entity in a given control plane.

Read the Plugin Reference and the Plugin Precedence sections for more information.

The following examples provide some typical configurations for enabling the Service Protection plugin globally.

Make the following request:

curl -X POST http://localhost:8001/plugins/ \
    --header "accept: application/json" \
    --header "Content-Type: application/json" \
    --data '
    {
  "name": "service-protection",
  "config": {
    "window_size": [
      30
    ],
    "window_type": "sliding",
    "limit": [
      5
    ],
    "namespace": "example_namespace"
  }
}
    '

Make the following request, substituting your own access token, region, and control plane ID:

curl -X POST \
https://{us|eu}.api.konghq.com/v2/control-planes/{controlPlaneId}/core-entities/plugins/ \
    --header "accept: application/json" \
    --header "Content-Type: application/json" \
    --header "Authorization: Bearer TOKEN" \
    --data '{"name":"service-protection","config":{"window_size":[30],"window_type":"sliding","limit":[5],"namespace":"example_namespace"}}'

See the Konnect API reference to learn about region-specific URLs and personal access tokens.

Create a KongClusterPlugin resource and label it as global:

apiVersion: configuration.konghq.com/v1
kind: KongClusterPlugin
metadata:
  name: <global-service-protection>
  annotations:
    kubernetes.io/ingress.class: kong
  labels:
    global: "true"
config:
  window_size:
  - 30
  window_type: sliding
  limit:
  - 5
  namespace: example_namespace
plugin: service-protection

Add a plugins entry in the declarative configuration file:

plugins:
- name: service-protection
  config:
    window_size:
    - 30
    window_type: sliding
    limit:
    - 5
    namespace: example_namespace
Prerequisite: Configure your Personal Access Token 
terraform {
  required_providers {
    konnect = {
      source  = "kong/konnect"
    }
  }
}

provider "konnect" {
  personal_access_token = "kpat_YOUR_TOKEN"
  server_url            = "https://us.api.konghq.com/"
}

Add the following to your Terraform configuration to create a Konnect Gateway Plugin:

resource "konnect_gateway_plugin_service_protection" "my_service_protection" {
  enabled = true

  config = {
    window_size = [30]
    window_type = "sliding"
    limit = [5]
    namespace = "example_namespace"
  }

  control_plane_id = konnect_gateway_control_plane.my_konnect_cp.id
}