Akamai API Security

Third Party

Overview Examples Configuration reference

Install the Akamai API Security plugin

Prerequisites

The Akamai API Security plugin requires the creation of an integration profile in API Security. For complete instructions, visit the Akamai API Security docs site.

Create the integration profile

Configure the integration profile in the Akamai API Security UI and download the plugin package:

In the Akamai API Security UI, navigate to Settings > Integrations > Traffic Sources.
Select Add Integration, then select the Kong tile to create an integration profile.
Download the zip file and copy it to your Kong Gateway machine, then select Next.
Provide an alias for the integration.
Select Finish to save the integration.

Choose your installation method

Unzip the plugin file you got from your integration profile. You’ll find the LuaRock file you need for the plugin installation.

Then, choose your installation method:

Use this method when Kong Gateway runs as a container and you build your own image.

Place the .rock file in the same directory as your Dockerfile, then add the following lines to your Dockerfile and build the image:

USER root

COPY ./kong-plugin-nonamesecurity-<version>.all.rock kong-plugin-nonamesecurity-<version>.all.rock

RUN luarocks install kong-plugin-nonamesecurity-<version>.all.rock

USER kong

Copied!

Run the container with nonamesecurity included in the KONG_PLUGINS list:
```
docker run -e "KONG_PLUGINS=bundled,nonamesecurity" ...
```
Copied!

Use this method when Kong Gateway is deployed on Kubernetes using the official Helm chart.

Unpack the plugin package and locate the kong/plugins/nonamesecurity/ directory.

Bundle the directory into a ConfigMap:

kubectl create configmap kong-plugin-nonamesecurity --from-file=nonamesecurity -n kong

Copied!

Update your Helm custom-values.yaml file to reference the ConfigMap:

plugins:
  configMaps:
    - pluginName: nonamesecurity
      name: kong-plugin-nonamesecurity

Copied!

Update your deployment using Helm:

helm upgrade kong kong/kong -n kong -f custom-values.yaml

Copied!

Verify that the plugin loaded:

kubectl logs -n kong deploy/kong-proxy | grep nonamesecurity

Copied!

Check the list of enabled plugins:

curl http://localhost:8001/plugins/enabled

Copied!

If you aren’t using Helm, add the following to the spec.container.env section of your Kong Deployment or DaemonSet instead:

env:
  - name: KONG_PLUGINS
    value: "bundled,nonamesecurity"

Copied!

Use this method when Kong Gateway runs directly on a host, for example RHEL, Debian, or Ubuntu.

Copy the .rock file to the Kong Gateway host.
Install it with LuaRocks. Use sudo if required, and use the absolute path (typically /usr/local/bin/luarocks) if luarocks isn’t in $PATH:
```
luarocks install kong-plugin-nonamesecurity-<version>.all.rock
```
Copied!
Confirm that the installed nonamesecurity folder has the same owner and permissions as your other Kong Gateway plugin folders. This is typically mode 777, owned by the kong:kong user and group.
Enable the plugin using one of the following options:

Update kong.conf:
```
plugins = bundled,nonamesecurity
```
Copied!
Or set the environment variable and restart Kong Gateway:
```
export KONG_PLUGINS="bundled,nonamesecurity"
```
Copied!
```
kong restart
```
Copied!

Konnect hybrid mode (self-managed data planes) is supported. Konnect Serverless and Dedicated Cloud Gateways can’t run custom plugins.

Upload the plugin schema so the control plane can validate and distribute Akamai API Security configuration.

Unpack the .rock file to get to schema.lua:
```
luarocks unpack kong-plugin-nonamesecurity-<version>.all.rock
```
Copied!
This creates a kong-plugin-nonamesecurity-<version>/nonamesecurity/schema.lua file relative to your current directory.

Set your Konnect credentials:

export KONNECT_TOKEN="your-konnect-personal-access-token"
export CONTROL_PLANE_ID="your-control-plane-id"

Copied!

Upload the schema, setting your own control plane ID and Konnect access token:

curl -i -X POST \
  "https://us.api.konghq.com/v2/control-planes/$CONTROL_PLANE_ID/core-entities/plugin-schemas" \
  --header "Authorization: Bearer $KONNECT_TOKEN" \
  --header "Content-Type: application/json" \
  --data "{\"lua_schema\": $(jq -Rs '.' kong-plugin-nonamesecurity-<version>/nonamesecurity/schema.lua)}"

Copied!

Install the .rock file (or a custom image containing it) on every data plane node, the same way you would for a Docker or Kubernetes deployment, and make sure nonamesecurity is included in KONG_PLUGINS on each data plane. Uploading a changed schema doesn’t push it to data planes on its own. Update or create another entity afterward so data planes pull the new payload.

Enable the plugin

Once installed, attach Akamai API Security at the global, Service, or Route level. See the Enable Akamai API Security example.

Akamai API Security

Install the Akamai API Security plugin

Prerequisites

Create the integration profile

Choose your installation method

Enable the plugin

Help us make these docs great!

Still need help?