While more and more organizations are seeking to standardize and consolidate their API and AI infrastructure efforts in a unified platform, the reality is that many — especially large — organizations already have disparate API deployments across disparate API gateways. One common API gateway that most enterprises have running at least somewhere is AWS API Gateway, as it is often seen as an easy-to-get-started-with solution for teams that are already running cloud workloads on AWS.
The disparate nature of a multi-gateway deployment causes many challenges for the enterprise, one being the lack of visibility and discoverability of API gateways and their associated APIs. This is a massive challenge for both human and non-human consumers (i.e., AI agents), as both need access to these resources to do their jobs, and it's a challenge to platform and security teams as API producers, as they can't secure and govern what they can't see.
We’re excited to announce that Konnect Service Catalog is beginning to tackle this problem with a native AWS integration that will enable organizations to discover and catalog APIs that they have running in AWS.
While multi-gateway vendor deployments have been found to be lacking as a long-term strategy, the reality is that every large organization is — at some point — going to struggle with trying to wrangle APIs across multiple API gateway solutions. This is especially true for the CSP-native API gateways.
Unfortunately, this presents massive problems around agentic consumption of APIs, as we know that agentic consumption of APIs is coming, with Gartner themselves finding that, by 2028, 50% of API consumption won’t involve a developer at all. And that, by 2029, 50% of API monetization will be driven by non-human API consumers. Who are these API consumers? They are AI agents, and they're coming for your APIs.
If they can find them.
Your agents will only ever be as good as what you feed them — and this includes API resources. Without centralized discoverability and access to all of the APIs across your org, your agents will be sorely lacking.
Service Catalog has already begun to solve for this through being able to surface APIs that are already under Kong Konnect management and APIs that aren’t through integrations with GitHub, GitLab, SwaggerHub, Traceable, and more.
Now, with the native integration with AWS, this discoverability benefit is widened, making discovery of your AWS API Gateway-managed APIs as easy as spinning up service catalog and pointing it at your AWS API Gateway instances.
Once the integration is configured, Service Catalog will begin to populate AWS API Gateway resources in the exact same catalog where all of your other API resources are catalogged — centrally within Konnect.
This means that now you can simply point your agents towards the Konnect Service Catalog, and they’ll have clear and easy access to discovering and consuming these APIs to do their jobs–and this might even mean making money for your organization (the billing and monetization part of this is something we can also solve for and will be talking about at API Summit).
While the agentic benefits of multi-gateway discovery are especially pertinent right now, there are also very important security and governance angles to AWS API Gateway discovery.
After all, you can’t secure and govern what you can’t see. And you can’t improve what you can’t measure.
This is where the combination of 360-degree discovery and Service Catalog scorecards become so powerful.
Once you’ve used Service Catalog to discover and catalog your API, AI, event streaming, and microservices assets, you can leverage Service Catalog scorecards to automate the measurement of how these various services comply with your specific organization's standards.
You can learn more here, but here is just a quick example:
Let’s say that, in order for your org to feel comfortable with an API or service being labeled as “production-ready," it must:
All of these criteria can be leveraged in Service Catalog scorecards. Once your scorecards are defined, they will be used to automatically measure how compliant your service is with the above criterion — ultimately giving them a score that can be surfaced to the relevant teams across your org. And, if the service isn’t compliant enough, not only will it have a low score, but it will also give insights into how to improve that score for quick remediation and resolution.
While this scorecard functionality isn’t new, being able to leverage it for APIs that are discovered from AWS is, and this gives your platform and governance teams yet another discoverability and governance tool in their toolbelt to extend their API governance reach.
We will be talking about API discovery and how it impacts AI and API strategy at API Summit 2025, live in New York City this October. If you want to learn more about the new functionality and how to introduce API and AI governance that is ready for the agentic era, make sure to register.
A quick refresher: Kong Cloud Gateways Kong Cloud Gateways are fully managed, high-performance data planes running on customer-dedicated infrastructure, orchestrated and operated by Kong through Kong Konnect . Customers can choose between: Serverle
The challenge: A disconnected world Consider the typical enterprise architecture in a relatively mature organization, an API management layer defines and deploys services to an API gateway, an Identity Provider (IDP) manages human user identities, a
We live in an API-driven economy , where Application Programming Interfaces (APIs) are increasingly being used to open new revenue channels, accelerate time to market and democratize data. Enterprises are constantly striving to build faster, more r
The challenges of an acquisition frequently appear in a number of critical areas, especially when dealing with a platform as important as Kafka: API Instability and Change : Merged entities frequently rationalize or re-architect their services, whic
Companies are charging headfirst into AI, with research around agentic AI in the enterprise finding as many as 9 out of 10 organizations are actively working to adopt AI agents. LLMs are being deployed, agentic workflows are getting created left
Bridging the API (and API access) gap between AI coding tools, agents, and the APIs that they “eat” Data might be the fuel for AI. But APIs are the proper way to package that “fuel” as AI-ready “food” is through the API. AI coding tools can do a lot
Introduction: It’s a great report for us here at Kong, and it further validates the changes happening in the larger market The 2025 Gartner Magic Quadrant for API Management report was a great one for us here at Kong. We continue to move “up and to