---
title: "Kong Agent"
slug: "kong-agent"
updated: 2026-06-22T07:01:56Z
published: 2026-06-22T07:01:56Z
canonical: "traceabledocs.document360.io/kong-agent"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://traceabledocs.document360.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Kong Agent

## 2.2.1 — 22nd April

### Updates

#### Added cloud metadata support for Kong running in AWS

The Kong plugin now collects cloud metadata for deployments running in AWS, including ECS, EC2, and EKS environments. Cloud metadata attributes such as `cloud.resource_id` are now captured and included in spans, enabling integrations that rely on cloud context, such as correlating API threats across Traceable and cloud security platforms.

---

## 2.2.0 — 17th January

### Updates

#### Added support for a token in the Kong plugin

The Kong plugin now supports configuring a token for authenticating with the Traceable platform. This allows deployments to pass an authentication token as part of the plugin configuration, enabling secure communication with the Traceable collector.

#### Added support for custom service naming using the Kong service name

The Kong plugin can now use the Kong service name as the service identifier in captured spans. This allows you to align the service name reported to Traceable with the service name defined in your Kong configuration, making it easier to correlate API traffic with the correct service in the Traceable platform.

#### Added support for service name prefix

The Kong plugin now supports configuring a prefix for service names reported to the Traceable platform. This allows you to namespace or distinguish service names across multiple environments or deployments by prepending a configurable string to the service name in captured spans.

#### Added Server-Sent Events (SSE) support (disabled by default)

The Kong plugin now includes support for Server-Sent Events (SSE). SSE support is disabled by default and can be enabled via configuration. This allows the plugin to handle SSE-based API traffic when needed, without affecting existing deployments that do not use SSE.