API Management with Kong Konnect Cloud

Test the Kong Konnect configuration by validating http port 8000 and https port 8443, review container logs and json configuration, and confirm local Kong gateway installation completed.

Configure Docker Desktop on Windows to install a local runtime instance as the data plane for Kong Konnect Cloud, enabling WSL2 and managing it via the cloud runtime manager.

Build a Kong gateway docker container with a batch script, connect the data plane to the runtime group in Kong Connect Cloud, and run Linux scripts on Windows via Ubuntu.

Install a Linux distribution on Windows using WSL and the virtual machine platform, then install Ubuntu and configure Docker integration. Run Kong's bash script to create a Kong Gateway container, add your user to the Docker group, restart, and verify ports 8008 and 8443.

Governs runtimes and their instances, the runtime manager enables adding or deleting runtime groups and stores state details; Connect Cloud provides the control plane and the data plane offers proxy.

Explore runtime groups as independent control planes in Kong Konnect Cloud, configuring gateway services, routes, consumers, plugins, upstreams, and certificates across gateway runtime instances.

Configure the runtime on your own across Windows, Linux, Mac, OS, and Kubernetes gateway. Monitor runtime group analytics and traffic, including the default runtime group and data plane gateway instance.

Explore the developer portal, a customization site for discovering and testing API services with docs, endpoints, and credential management, published from Service Hub for developer registration.

Developers access APIs through the developer portal by signing up and awaiting approval in Kong manager. They create an app, associate services, and log in after approval.

Log into the developer portal and create an app with a unique name and reference id, generate a 32-character api key as credentials, and associate services from the catalog.

Create a gateway service in Kong Konnect Cloud to proxy traffic to a backend API via a route, using a runtime group and a url or host and path.

Create a route for the gateway service to expose the backend API via get customer path. Root serves as the client entry point.

Configure the request termination plugin to reject all incoming requests, choosing a status code, content type, and body or message, then test the gateway service for default and customized responses.

Learn to secure resources with JSON Web Tokens (JWT) in Kong Konnect Cloud, using 256 signing with a shared or public/private key, and configure headers and claims for authorization.

Configure the bot detection plugin in Kong Konnect Cloud to protect the API proxy using a user agent deny list, and validate blocking of Postman, Edge, Chrome, and curl requests.

Configure an upstream object as a virtual host to load balance requests across two targets. Use round robin with health checks and a gateway service to route to backend APIs.

Install Docker Desktop on Windows, enable WSL 2, log in to Docker Hub, and run a container to explore images, containers, gateway runtime, and switch between Linux and Windows containers.