Event Gateway Documentation

A Kafka proxy for controlled, secure client access to your Kafka cluster—both internal and external.

How does Kong Event Gateway work?

An overview of policies that work with Event Gateway.

Get started with Kong Event Gateway by setting up a demo Konnect control plane and data plane, then configuring a backend cluster, virtual cluster, listener, and policies with the Kong Event Gateway API.

Backend clusters represent target Kafka clusters proxies by Kong Event Gateway.

Listeners represent the network interface for Kafka client connections over TCP.

Virtual clusters are Event Gateway entities that expose a modified view of the backend cluster to clients.

Policies control how Kafka protocol traffic is modified between the client and the backend cluster.

Schema registries are resources that let you validate messages against the Confluent schema registry.

Static encryption keys are resources that can be used by the Encrypt and Decrypt policies to encrypt and decrypt Kafka messages.

Manage access to your virtual cluster resources.

Decrypt messages that were previously encrypted using the referenced key

Encrypt portions of Kafka records

Forward messages from a Kafka client to a virtual cluster

Set or remove record headers

Validate records against a schema during the consume phase

Validate records against a schema during the produce phase

Skip the processing of a record

Configure TLS settings for a server

Use namespaces and ACL policies to create products from Kafka topics.

Use this tutorial to encrypt and decrypt Kafka messages with Kong Event Gateway using a static key.

OpenAPI specification for the Kong Event Gateway Control Plane API.

Reference for Kong Event Gateway data plane configuration parameters.

Reference for the expressions language used for defining Event Gateway conditions.

This page lists the current Kong Event Gateway limitations.