Red Hat OpenShift is the industry's leading enterprise Kubernetes platform that runs ubiquitously across on-prem, and the cloud. With Red Hat OpenShift Service on AWS (ROSA), a managed Red Hat OpenShift platform that runs natively on AWS, it is even easier to get kick-started on an enterprise-ready instance of Red Hat OpenShift in the cloud.
Kong similarly distinguishes itself as a multi-platform, multi-cloud API Management solution pushing the vision of APIs. Here at Kong, we want to demonstrate to the Red Hat community that we are committed to delivering enterprise-grade solutions.
In this climate of technology, the top two concerns organizations are facing today are, first, how to manage the sprawl of APIs as they distribute across a multi-platform, hybrid cloud ecosystem. Second, in this same landscape, how to deliver secure APIs with a strategy that can be applied ubiquitously across their hybrid cloud infrastructure.
APISecOps in a Hybrid Cloud. How do we take action on this?
To answer this question, we built a tutorial to walk you through an end-to-end APISecOps solution. You will learn how the four principles of APISecOps — Centralization, Governance, API Design-First, and GitOps — can be applied to build secure APIs in a hybrid cloud ecosystem.
For this tutorial the tooling will be as follows:
You will start with configuring the infrastructure by running an Ansible playbook to configure Kong Konnect Gateways on ROSA. Each gateway will be associated with a Konnect Runtime Group (Sandbox/Default and Dev) to demonstrate the API promotion scheme.
Then you will get your hands dirty by walking through the APISecOps pipeline yourself. APISecOps begins with API Design-First phase by updating an API Spec in Kong Insomnia, Kong's API design and testing suite.
This will follow with stepping through several Tekton Pipelines to pass the API spec through governance review, convert the API Spec to Kong's decK manifest and finally, promoted to the two environments. For this demo, we've taken the time to build Tekton Tasks for the Inso CLI and deck CLI too that are designed to support API pipelines and Kong gateway manifests.
Then you will close off with a demonstration of how to host your API documentation in Konnect with Service Hub and Dev Portal.
Check out the Kong APISecOps repository on GitHub!
We also have corresponding videos on YouTube that walk you through the entire tutorial! Don't be too nervous, each video is about 5-8 min long:
Check out our blog post How APISecOps Protects Against API Abuse to learn about APISecOps best practices.
Meet Emily. She’s an API product manager at ACME, Inc., an ecommerce company that runs on dozens of APIs. One morning, her team lead asks a simple question: “Who’s our top API consumer, and which of your APIs are causing the most issues right now?”
Today, we’re announcing that Kong has acquired OpenMeter , the open source and SaaS leader for real-time usage metering and billing. OpenMeter’s capabilities will be integrated into Kong Konnect, enabling usage-based pricing, entitlements, and invo
It’s been almost a year since we released our Konnect Terraform provider . In that time we’ve seen over 300,000 installs, have 1.7 times as many resources available, and have expanded the provider to include data sources to enable federated managem
In the last two parts of this series, we discussed How to Strengthen a ReAct AI Agent with Kong AI Gateway and How to Build a Single-LLM AI Agent with Kong AI Gateway and LangGraph . In this third and final part, we're going to evolve the AI Agen
In my previous post, we discussed how we can implement a basic AI Agent with Kong AI Gateway. In part two of this series, we're going to review LangGraph fundamentals, rewrite the AI Agent and explore how Kong AI Gateway can be used to protect an LLM
We're happy to announce the 3.5 release of Kong Ingress Controller (KIC). This release includes the graduation of combined services to General Availability, support for connection draining, as well as the start of deprecating support for some Ingre
This is part one of a series exploring how Kong AI Gateway can be used in an AI Agent development with LangGraph. The series comprises three parts: Basic ReAct AI Agent with Kong AI Gateway Single LLM ReAct AI Agent with Kong AI Gateway and LangGr