Install Kong Gateway

Kong Gateway is a low-demand, high-performing API gateway. You can set up Kong Gateway with Konnect, or install it on various self-managed systems.

Uses: Kong Gateway

Konnect is Kong's SaaS platform for running Kong Gateway without any infrastructure to manage. Get a fully managed Control Plane, real-time analytics, and enterprise-grade security.

Sign up for free →

Linux

Package manager

curl -1sLf "https://packages.konghq.com/public/gateway-311/gpg.CF9CDA9D288571F9.key" |  gpg --dearmor | sudo tee /usr/share/keyrings/kong-gateway-311-archive-keyring.gpg > /dev/null
curl -1sLf "https://packages.konghq.com/public/gateway-311/config.deb.txt?distro=debian&codename=$(lsb_release -sc)" | sudo tee /etc/apt/sources.list.d/kong-gateway-311.list > /dev/null
sudo apt-get update && sudo apt install -y kong-enterprise-edition=3.11.0.0

After installation, configure the datastore to complete setup.

Binary Download

AMD64

3.11.0.0

ARM64

3.11.0.0

Package manager

curl -1sLf "https://packages.konghq.com/public/gateway-311/gpg.CF9CDA9D288571F9.key" |  gpg --dearmor | sudo tee /usr/share/keyrings/kong-gateway-311-archive-keyring.gpg > /dev/null
curl -1sLf "https://packages.konghq.com/public/gateway-311/config.deb.txt?distro=ubuntu&codename=noble" | sudo tee /etc/apt/sources.list.d/kong-gateway-311.list > /dev/null
sudo apt-get update && sudo apt-get install -y kong-enterprise-edition=3.11.0.0

Note: Kong Gateway is packaged for Focal, Jammy, Noble. The snippet above assumes you are running Noble. Replace it with your release. To check the name of your release, run lsb_release -sc.

After installation, configure the datastore to complete setup.

Binary Download

AMD64

3.11.0.0

ARM64

3.11.0.0

AMD64 - FIPS

3.11.0.0

For FIPS-compliant environments, you must also enable fips = on in your Kong configuration file.

Package manager

curl -1sLf "https://packages.konghq.com/public/gateway-311/config.rpm.txt?distro=el&codename=$(rpm --eval '%{rhel}')" | sudo tee /etc/yum.repos.d/kong-gateway-311.repo
sudo yum -q makecache -y --disablerepo='*' --enablerepo='kong-gateway-311'
sudo yum install -y kong-enterprise-edition-3.11.0.0

After installation, configure the datastore to complete setup.

Binary Download

AARCH64

3.11.0.0

X86_64

3.11.0.0

X86_64 - FIPS

3.11.0.0

For FIPS-compliant environments, you must also enable fips = on in your Kong configuration file.

Package manager

curl -1sLf "https://packages.konghq.com/public/gateway-311/config.rpm.txt?distro=amzn&codename=$(rpm --eval '%{amzn}')" | sudo tee /etc/yum.repos.d/kong-gateway-311.repo > /dev/null
sudo yum -q makecache -y --disablerepo='*' --enablerepo='kong-gateway-311'
sudo yum install -y kong-enterprise-edition-3.11.0.0

After installation, configure the datastore to complete setup.

Binary Download

AARCH64

3.11.0.0

X86_64

3.11.0.0

Docker

Using Docker Compose

Kong Gateway is available as a Docker image, making it easy to deploy in containerized environments.

Install via Docker →

Build your own

Kong Gateway is distributed as prebuilt deb and rpm packages, in addition to official Docker images hosted on Docker Hub.

Build your own Docker image →

Kubernetes

Deploy Kong Gateway on Kubernetes

Deploy Kong Gateway on Kubernetes, and configure it using the UI, decK or Terraform.

Install via Helm → Install via Kong Gateway Operator →

Install Kong Ingress Controller (KIC)

Configure Kong Gateway using Kubernetes-native resources such as httproute and ingress.

Install via Helm → Install via Kong Gateway Operator →

FAQs

How do I migrate from Kong Gateway open source (OSS) to Kong Gateway Enterprise?

You can migrate to Kong Gateway Enterprise using the kong migrations CLI commands.

Warning: This action is irreversible, therefore we strongly recommend backing up your production data before migrating from Kong Gateway OSS to Kong Gateway Enterprise.

You can only migrate to a Kong Gateway Enterprise version that supports the same OSS version. For example, if you want to migrate to Kong Gateway Enterprise 3.10, you must upgrade to Kong Gateway OSS 3.10 first.

Download the Kong Gateway Enterprise package and configure it to point to the same data store as your Kong Gateway OSS node. The migration command expects the data store to be up to date on any pending migration:
```
kong migrations up [-c configuration_file]
kong migrations -f finish [-c configuration_file]
```
Caution: When adding new plugins to the existing installation (either manually or via the extension of bundled plugins), the kong migrations finish or kong migrations up must be run with the -f flag to forcefully upgrade the plugin schemas.
Confirm that all of the entities are now available on your Kong Gateway Enterprise node.

Install Kong Gateway

Linux

Package manager

Binary Download

Package manager

Binary Download

Package manager

Binary Download

Package manager

Binary Download

Docker

Using Docker Compose

Build your own

Kubernetes

Deploy Kong Gateway on Kubernetes

Install Kong Ingress Controller (KIC)

FAQs

Help us make these docs great!

Still need help