Serverless gateways are lightweight API gateways. Their Control Plane is hosted by Konnect and Data Plane nodes are automatically provisioned. Serverless gateways are ideal for developers who want to test or experiment in a pre-production environment.
You can manage your serverless gateway nodes in Gateway Manager.
When you create a serverless gateway, Konnect creates a Control Plane that is hosted by Konnect. Then, a hosted Data Plane is provisioned automatically and configured to connect to the Control Plane.
flowchart TD
A(Dev Portal • Gateway Manager • Advanced Analytics • Service Catalog)
B( Kong-managed Control Plane #40;Kong Gateway instance#41;)
C( Data Plane #40;Kong Gateway instance#41;)
subgraph id1 [Konnect]
A --- B
end
B --Kong proxy
configuration---> id2
subgraph id2 [Fully-managed cloud nodes]
C
end
style id1 stroke-dasharray:3,rx:10,ry:10
style id2 stroke-dasharray:3,rx:10,ry:10
Provisioning a serverless gateway includes creating the serverless Control Plane and hosted Data Plane.
Create a serverless gateway Control Plane by issuing a POST request to the Control Plane API.
curl -X POST "$KONNECT_CONTROL_PLANE_URL/v2/control-planes/$CONTROL_PLANE_ID/"\-H"Accept: application/json"\-H"Content-Type: application/json"\-H"Authorization: Bearer $KONNECT_TOKEN"\--json'{
"name": "serverless-gateway-control-plane",
"description": "A test Control Plane for Serverless Gateways.",
"cluster_type": "CLUSTER_TYPE_SERVERLESS",
"cloud_gateway": false,
"auth_type": "pinned_client_certs"
}'
Create a hosted Data Plane by issuing a PUT request to the Cloud Gateways API:
Navigate to the DNS settings section. This area might be labeled differently depending on your registrar.
Locate the option to add a new CNAME record and create the following record using the CNAME value from Konnect that you saved previously. For example, in AWS Route 53, it would look like this:
Host Name
Record Type
Routing Policy
Alias
Evaluate Target Health
Value
TTL
my.example.com
CNAME
Simple
9e454bcfec.kongcloud.dev
300
Once a Serverless Gateway custom DNS record has been validated, it will not be refreshed or re-validated. Remove and re-add the custom domain in Konnect to force a re-validation.
Serverless gateways only support public networking. If your use case requires private connectivity, consider using Dedicated Cloud Gateways with AWS Transit Gateways.
To securely connect a serverless gateway to your backend, you can inject a shared secret into each request using the Request Transformer plugin.
Ensure the backend accepts a known token like an Authorization header.
Attach a new plugin to the Control Plane and Gateway Service that you want to secure:
No, serverless gateways only supports public networking. There are currently no capabilities for private networking between your data centers and hosted Kong Data Planes. For use cases where private networking is required, Dedicated Cloud Gateways configured with AWS is a better choice.
If your custom domain attachment fails, check if your domain has a Certificate Authority Authorization (CAA) record restricting certificate issuance. Serverless Gateways use Let’s Encrypt CA to provision SSL/TLS certificates. If your CAA record doesn’t include the required CA, certificate issuance will fail.
You can resolve this issue by doing the following:
Check existing CAA records by running dig CAA yourdomain.com +short.
If a CAA record exists but doesn’t allow Let’s Encrypt (letsencrypt.org), update it.
Update the CAA record, if needed. For example: yourdomain.com. CAA 0 issue "letsencrypt.org"
Wait for DNS propagation and retry attaching your domain.
If no CAA record exists, no changes are needed. For more information, see the Let’s Encrypt CAA Guide.