Certificate
objectA certificate object represents a public certificate. These fields are referenceable, and can be stored as secrets in a vault. References must follow a specific format.
PEM-encoded public certificate chain of the SSL key This field is referenceable and can be stored in a vault. References must follow a specific format.
Example:-----BEGIN CERTIFICATE-----\ncertificate-content\n-----END CERTIFICATE-----
PEM-encoded public certificate chain of the alternate SSL key pair. This should only be set if you have both RSA and ECDSA types of certificate available and would like Kong to prefer serving using ECDSA certs.
Example:-----BEGIN CERTIFICATE-----...
Unix epoch when the resource was created.
Example:1422386534
Unix epoch when the resouce was updated.
Example:1422386534
The UUID representation of the certificate object.
Example:7fca84d6-7d37-4a74-a7b0-93e576089a41
PEM-encoded private key of the SSL key pair. This field is referenceable, which means it can be securely stored as a secret in a vault. References must follow a specific format.
Example: -----BEGIN RSA PRIVATE KEY-----...
PEM-encoded private key of the alternate SSL key pair. This should only be set if you have both RSA and ECDSA types of certificate available and would like Kong to prefer serving using ECDSA certs when client advertises support for it. This field is referenceable, which means it can be securely stored as a secret in a vault. References must follow a specific format.
Example:-----BEGIN EC PRIVATE KEY-----...
An optional set of strings associated with the Certificate for grouping and filtering.
Example:user-level
Key
objectA Key object holds a representation of asymmetric keys in various formats. When Kong or a Kong plugin requires a specific public or private key to perform certain operations, it can use this entity.
Unix epoch when the resource was created.
Example:1422386534
The unique identifier or the prefix of the Vault to delete.
Example:24D0DBDA-671C-11ED-BA0B-EF1DCCD3725F
A JSON Web Key represented as a string.
Example:{\alg\:\RSA\, \kid\: \42\, ...}
A unique identifier for a key.
Example:42
Unix epoch when the resouce was updated.
Example:1422386534
A keypair in PEM format.
Show Child Parameters
The id (an UUID) of the key-set with which to associate the key.
Show Child Parameters
An optional set of strings associated with the Key for grouping and filtering.
Plugin
objectA Plugin entity represents a plugin configuration that will be executed during the HTTP request/response lifecycle.
The configuration properties for the Plugin which can be found on the plugins documentation page in the Kong Hub.
If set, the plugin will activate only for requests where the specified has been authenticated. (Note that some plugins can not be restricted to consumers this way.). Leave unset for the plugin to activate regardless of the authenticated Consumer.
Show Child Parameters
Unix epoch when the resource was created.
Whether the plugin is applied.
Default:true
The name of the Plugin that’s going to be added. Currently, the Plugin must be installed in every Kong instance separately.
A list of the request protocols that will trigger this plugin. The default value, as well as the possible values allowed on this field, may change depending on the plugin type. For example, plugins that only work in stream mode will only support tcp and tls.
Default:grpc, grpcs, http, https
If set, the plugin will only activate when receiving requests via the specified route. Leave unset for the plugin to activate regardless of the route being used.
Show Child Parameters
If set, the plugin will only activate when receiving requests via one of the routes belonging to the specified service. Leave unset for the plugin to activate regardless of the service being matched.
Show Child Parameters
An optional set of strings associated with the Plugin for grouping and filtering.
Route
objectRoute entities define rules to match client requests. Every request matching a given route will be proxied to its associated service.
Unix epoch when the resource was created.
A list of IP destinations of incoming connections that match this route when using stream routing. Each entry is an object with fields ip (optionally in CIDR range notation) and/or port.
One or more lists of values indexed by header name that will cause this route to match if present in the request. The Host header cannot be used with this attribute: hosts should be specified using the hosts attribute. When headers contains only one value and that value starts with the special prefix ~*, the value is interpreted as a regular expression.
A list of domain names that match this route. Note that the hosts value is case sensitive.
Example:foo.example.com
The status code Kong responds with when all properties of a route match except the protocol i.e. if the protocol of the request is HTTP instead of HTTPS. Location header is injected by Kong if the field is set to 301, 302, 307 or 308. Note: This config applies only if the route is configured to only accept the https protocol.
Default:426
Example:56c4566c-14cc-4132-9011-4139fcbbe50a
A list of HTTP methods that match this route.
The name of the route. Route names must be unique, and they are case sensitive. For example, there can be two different routes named test and Test.
Controls how the service path, route path and requested path are combined when sending a request to the upstream. See above for a detailed description of each behavior.
Default:v0
A list of paths that match this route.
When matching a route via one of the hosts domain names, use the request Host header in the upstream request headers. If set to false, the upstream Host header will be that of the service’s host.
Default:false
An array of the protocols this route should allow. See the route Object section for a list of accepted protocols. When set to only https, HTTP requests are answered with an upgrade error. When set to only http, HTTPS requests are answered with an error.
Default:http, https
A number used to choose which route resolves a given request when several routes match it using regexes simultaneously. When two routes match the path and have the same regex_priority, the older one (lowest created_at) is used. Note that the priority for non-regex routes is different (longer non-regex routes are matched before shorter ones).
Default:0
Whether to enable request body buffering or not. With HTTP 1.1, it may make sense to turn this off on services that receive data with chunked transfer encoding.
Default:true
Whether to enable response body buffering or not. With HTTP 1.1, it may make sense to turn this off on services that send data with chunked transfer encoding.
Default:true
The service this route is associated to. This is where the route proxies traffic to.
Show Child Parameters
A list of SNIs that match this route when using stream routing.
A list of IP sources of incoming connections that match this route when using stream routing. Each entry is an object with fields ip (optionally in CIDR range notation) and/or port.
When matching a route via one of the paths, strip the matching prefix from the upstream request URL.
Default:true
An optional set of strings associated with the route for grouping and filtering.
Unix epoch when the resource was last updated.
SNI
objectAn SNI object represents a many-to-one mapping of hostnames to a certificate. That is, a certificate object can have many hostnames associated with it; when Kong receives an SSL request, it uses the SNI field in the Client Hello to lookup the certificate object based on the SNI associated with the certificate.
The id (a UUID) of the certificate with which to associate the SNI hostname. The Certificate must have a valid private key associated with it to be used by the SNI object.
Show Child Parameters
Unix epoch when the resource was created.
Example:1422386534
Example:b87eb55d-69a1-41d2-8653-8d706eecefc0
The SNI name to associate with the given certificate.
Example:my-sni
An optional set of strings associated with the SNIs for grouping and filtering.
Example:user-level, enterprise