Third Party Tools

These are services which are used in day to day operation of Kong Gateway. Use of these services may be optional, or they may be required by certain plugins.

Unless otherwise noted, Kong supports the last 2 versions any third party tool, plus the current managed version if available.

Some third party tools below do not have a version number. These tools are managed services and Kong provides compatibility with the currently released version

3.3

3.2

3.1

3.0

2.8 LTS

Data Stores

Kong interacts with multiple data stores during normal operation. The following stores have been tested by Kong:

Postgres 15, 14, 13, 12, 11, 10, 9, Amazon RDS, Amazon Aurora

Cassandra 3.11

Redis 6, 7, AWS Elasticache

InfluxDB 1

Kafka 3.3, 3.2, Confluent Cloud

Vaults

Kong allows you to store secret values in external vaults. The following versions have been tested by Kong:

Hashicorp Vault
1.12

AWS Secrets Manager

Google Secrets Manager

Service Mesh

Kong Ingress Controller has been tested against the following Service Mesh versions:

Kong Mesh
2.0

Istio
1.16, 1.15, 1.14

Metrics

Kong Ingress Controller has been tested against the following metrics providers:

Prometheus 2.4, 2.37

statsd 0.9

OpenTelemetry

Zipkin 2.23, 2.22

Log Providers

Kong Ingress Controller has been tested against the following log providers:

Splunk

Datadog

Loggly

S3 Compatible APIs

Any S3 compatible API is available for use when working with remote file storage. The following have been tested by Kong:

AWS S3

MinIO

Identity Providers

Kong is expected to work with the following third party identity providers (IDP) when using the OpenID Connect (OIDC) plugin:

• Auth0

• AWS Cognito

• Connect2id

• Curity

• Dex

• Gluu

• Google

• IdentityServer

• Keycloak

• Microsoft Azure Active Directory

• Microsoft Active Directory Federation Services

• Microsoft Live Connect

• Okta

• OneLogin

• OpenAM

• Paypal

• PingFederate

• Salesforce

• WSO2

• Yahoo!

Data Stores

Kong interacts with multiple data stores during normal operation. The following stores have been tested by Kong:

Postgres 15, 14, 13, 12, 11, 10, 9, Amazon RDS

Cassandra 3.11

Redis 6, 7, AWS Elasticache

InfluxDB 1

Kafka 3.3, 3.2, Confluent Cloud

Vaults

Kong allows you to store secret values in external vaults. The following versions have been tested by Kong:

Hashicorp Vault
1.12

AWS Secrets Manager

Google Secrets Manager

Service Mesh

Kong Ingress Controller has been tested against the following Service Mesh versions:

Kong Mesh
2.0

Istio
1.16, 1.15, 1.14

Metrics

Kong Ingress Controller has been tested against the following metrics providers:

Prometheus 2.4, 2.37

statsd 0.9

OpenTelemetry

Zipkin 2.23, 2.22

Log Providers

Kong Ingress Controller has been tested against the following log providers:

Splunk

Datadog

Loggly

S3 Compatible APIs

Any S3 compatible API is available for use when working with remote file storage. The following have been tested by Kong:

AWS S3

MinIO

Identity Providers

Kong is expected to work with the following third party identity providers (IDP) when using the OpenID Connect (OIDC) plugin:

• Auth0

• AWS Cognito

• Connect2id

• Curity

• Dex

• Gluu

• Google

• IdentityServer

• Keycloak

• Microsoft Azure Active Directory

• Microsoft Active Directory Federation Services

• Microsoft Live Connect

• Okta

• OneLogin

• OpenAM

• Paypal

• PingFederate

• Salesforce

• WSO2

• Yahoo!

Data Stores

Kong interacts with multiple data stores during normal operation. The following stores have been tested by Kong:

Postgres 15, 14, 13, 12, 11, 10, 9, Amazon RDS

Cassandra 3.11

Redis 6, 7, AWS Elasticache

InfluxDB 1

Kafka 3.3, 3.2, Confluent Cloud

Vaults

Kong allows you to store secret values in external vaults. The following versions have been tested by Kong:

Hashicorp Vault
1.12

AWS Secrets Manager

Google Secrets Manager

Service Mesh

Kong Ingress Controller has been tested against the following Service Mesh versions:

Kong Mesh
2.0

Istio
1.16, 1.15, 1.14

Metrics

Kong Ingress Controller has been tested against the following metrics providers:

Prometheus 2.4, 2.37

statsd 0.9

OpenTelemetry

Zipkin 2.23, 2.22

Log Providers

Kong Ingress Controller has been tested against the following log providers:

Splunk

Datadog

Loggly

S3 Compatible APIs

Any S3 compatible API is available for use when working with remote file storage. The following have been tested by Kong:

AWS S3

MinIO

Identity Providers

Kong is expected to work with the following third party identity providers (IDP) when using the OpenID Connect (OIDC) plugin:

• Auth0

• AWS Cognito

• Connect2id

• Curity

• Dex

• Gluu

• Google

• IdentityServer

• Keycloak

• Microsoft Azure Active Directory

• Microsoft Active Directory Federation Services

• Microsoft Live Connect

• Okta

• OneLogin

• OpenAM

• Paypal

• PingFederate

• Salesforce

• WSO2

• Yahoo!

Data Stores

Kong interacts with multiple data stores during normal operation. The following stores have been tested by Kong:

Postgres 15, 14, 13, 12, 11, 10, 9, Amazon RDS

Cassandra 3.11

Redis 6, 7, AWS Elasticache

InfluxDB 1

Kafka 3.3, 3.2, Confluent Cloud

Vaults

Kong allows you to store secret values in external vaults. The following versions have been tested by Kong:

Hashicorp Vault
1.12

AWS Secrets Manager

Google Secrets Manager

Service Mesh

Kong Ingress Controller has been tested against the following Service Mesh versions:

Kong Mesh
2.0

Istio
1.16, 1.15, 1.14

Metrics

Kong Ingress Controller has been tested against the following metrics providers:

Prometheus 2.4, 2.37

statsd 0.9

OpenTelemetry

Zipkin 2.23, 2.22

Log Providers

Kong Ingress Controller has been tested against the following log providers:

Splunk

Datadog

Loggly

S3 Compatible APIs

Any S3 compatible API is available for use when working with remote file storage. The following have been tested by Kong:

AWS S3

MinIO

Identity Providers

Kong is expected to work with the following third party identity providers (IDP) when using the OpenID Connect (OIDC) plugin:

• Auth0

• AWS Cognito

• Connect2id

• Curity

• Dex

• Gluu

• Google

• IdentityServer

• Keycloak

• Microsoft Azure Active Directory

• Microsoft Active Directory Federation Services

• Microsoft Live Connect

• Okta

• OneLogin

• OpenAM

• Paypal

• PingFederate

• Salesforce

• WSO2

• Yahoo!

Data Stores

Kong interacts with multiple data stores during normal operation. The following stores have been tested by Kong:

Postgres 15, 14, 13, 12, 11, 10, 9, Amazon RDS

Cassandra 3.11

Redis 6, 7, AWS Elasticache

InfluxDB 1

Kafka 3.3, 3.2, Confluent Cloud

Vaults

Kong allows you to store secret values in external vaults. The following versions have been tested by Kong:

Hashicorp Vault
1.12

AWS Secrets Manager

Google Secrets Manager

Service Mesh

Kong Ingress Controller has been tested against the following Service Mesh versions:

Kong Mesh
2.0

Istio
1.16, 1.15, 1.14

Metrics

Kong Ingress Controller has been tested against the following metrics providers:

Prometheus 2.4, 2.37

statsd 0.9

OpenTelemetry

Zipkin 2.23, 2.22

Log Providers

Kong Ingress Controller has been tested against the following log providers:

Splunk

Datadog

Loggly

S3 Compatible APIs

Any S3 compatible API is available for use when working with remote file storage. The following have been tested by Kong:

AWS S3

MinIO

Identity Providers

Kong is expected to work with the following third party identity providers (IDP) when using the OpenID Connect (OIDC) plugin:

• Auth0

• AWS Cognito

• Connect2id

• Curity

• Dex

• Gluu

• Google

• IdentityServer

• Keycloak

• Microsoft Azure Active Directory

• Microsoft Active Directory Federation Services

• Microsoft Live Connect

• Okta

• OneLogin

• OpenAM

• Paypal

• PingFederate

• Salesforce

• WSO2

• Yahoo!