Skip to content
Kong Logo | Kong Docs Logo
search
  • We're Hiring!
  • Docs
    • Kong Gateway
    • Kong Konnect
    • Kong Mesh
    • Plugin Hub
    • decK
    • Kubernetes Ingress Controller
    • Insomnia
    • Kuma

    • Docs contribution guidelines
  • Plugin Hub
  • Support
  • Community
  • Kong Academy
Early Access
  • Kong Gateway
  • Kong Konnect
  • Kong Mesh
  • Plugin Hub
  • decK
  • Kubernetes Ingress Controller
  • Insomnia
  • Kuma

  • Docs contribution guidelines
    • Overview of Konnect
    • Architecture
    • Network Resiliency and Availability
    • Port and Network Requirements
    • Compatibility
    • Stages of Software Availability
    • Release Notes
      • Control Plane Upgrades FAQ
      • Supported Installation Options
    • Overview
    • Access a Konnect Account
    • Set up a Runtime
    • Configure a Service
    • Implement and Test the Service
      • Publish and Consume Services
      • Register Applications
    • Import Kong Gateway Entities into Konnect
    • Overview
      • Overview
      • Dashboard
      • Manage Runtime Groups with UI
      • Manage Runtime Groups with decK
      • Installation Options
      • Install with Docker
      • Install on Kubernetes
      • Install on Linux
      • Install on AWS
      • Install on Azure
      • Upgrade a Runtime Instance to a New Version
      • Renew Certificates
      • Runtime Parameter Reference
      • Overview
      • Runtime Configuration
    • Create Consumer Groups
      • Overview
      • Set Up and Use a Vault in Konnect
    • Plugin Ordering Reference
    • Troubleshoot
    • Overview
      • Konnect Services
      • Service Versions
      • Service Implementations
      • Manage Service Documentation
      • Overview
      • Configure a Plugin on a Service
      • Configure a Plugin on a Route
    • Overview
    • Access the Dev Portal
    • Sign Up for a Dev Portal Account
      • Manage Developer Access
      • Manage Application Registration Requests
      • Manage Application Connections
      • Auto Approve Dev and App Registrations
      • Azure OIDC
      • Application Overview
      • Enable and Disable App Registration
        • Okta
        • Curity
        • Auth0
      • Create, Edit, and Delete an Application
      • Register an Application with a Service
      • Generate Credentials for an Application
    • Customize Dev Portal
    • Troubleshoot
    • Introduction to Analytics
    • Summary Dashboard
    • Analyze Services and Routes
    • Generate Reports
    • Troubleshoot
      • Manage a Konnect Account or Plan
      • Change to a Different Plan
      • Manage Payment Methods and Invoices
      • Overview
        • Overview
        • Manage Teams
        • Teams Reference
        • Roles Reference
      • Manage Users
      • Set up SSO with OIDC
      • Set up SSO with Okta
    • Account and Org Deactivation
    • Troubleshoot
    • Overview
      • API Documentation
      • Identity Integration Guide
      • API Documentation
      • Overview
      • Nodes
      • Data Plane Certificiates
        • Services
        • Routes
        • Consumers
        • Plugins
        • Upstreams
        • Certificates
        • CA Certificates
        • SNIs
        • Targets
        • Vaults
      • API Spec
      • Filtering

github-edit-pageEdit this page

report-issueReport an issue

enterprise-switcher-iconSwitch to OSS

On this page
  • Services in the Service Hub catalog
    • Kong Gateway implementations
  • Dev Portal
  • Kong Gateway plugins
Kong Konnect
  • Home
  • Kong Konnect
  • Service Hub Overview

Service Hub Overview

The Service Hub is a Kong Konnect functionality module that lets you catalog all of your services in a single system of record. This catalog represents the single source of truth of your organization’s service inventory and their dependencies.

Using the Service Hub, you can catalog, manage, and track every service in your entire architecture.

Services in the Service Hub catalog

Each entry in the Service Hub is called a Konnect service, or service. A Konnect service is an abstraction of an upstream service.

A service in the Service Hub breaks down into multiple configuration versions, and can be implemented to route to any endpoint.

Konnect service diagram

  • Service: The abstraction of one of your own services. For example, it might represent a data transformation microservice or a billing API.

  • Service version: One instance, or implementation, of the service with a unique configuration. A service can have many versions, and each version can have different configurations, set up for a RESTful API, gPRC endpoint, GraphQL endpoint, and others.

  • Service implementation: A runnable service version. Each service version can only have one implementation.

A Konnect service isn’t associated with any specific runtime group, but every service version is. When you create a version of the service, you must select a group for the version to run on.

Note: Currently, the only supported implementation type is a Kong Gateway runtime.

The main attribute of a service version is its upstream URL, where the service listens for requests. You can specify the URL with a single string, or by specifying its protocol, host, port, and path individually.

Get started with service management →

Kong Gateway implementations

When configuring a Kong Gateway implementation of a service, you’ll need to specify a route. Routes determine how successful requests are sent to their services after they reach the API gateway. A single service version can have only one implementation, but potentially many routes.

Important: Starting with Kong Gateway 3.0.0.0, the router supports logical expressions. Regex routes must begin with a ~ character. For example: ~/foo/bar/(?baz\w+). Learn more in the route configuration guide.

After configuring the service, version, implementation, and at least one route, you’ll be able to start making requests through Kong Konnect.

Implement a service version →

Dev Portal

Service Hub natively integrates the Dev Portal into service configuration. Admins can publish services directly from Service Hub to the Dev Portal, where application developers can search, discover, and consume existing services.

The Dev Portal in Kong Konnect contains an API catalog, allowing you to document all of your services and their versions.

Through Service Hub, publish your service to the Dev Portal and set up the following for any service:

  • Markdown documentation: A description of your service. Applies to every service version.
  • Version spec: An OpenAPI (Swagger) document in YAML or JSON format. Applies to a specific service version.

Upload and publish service documentation to the Dev Portal →

Kong Gateway plugins

Plugins can be configured to run in a variety of contexts, ranging from a specific service version or route to all service versions. Plugins can execute actions inside Kong Konnect before or after a request has been proxied to the upstream API, as well as on any incoming responses.

Manage plugins →

Thank you for your feedback.
Was this page useful?
  • Kong
    THE CLOUD CONNECTIVITY COMPANY

    Kong powers reliable digital connections across APIs, hybrid and multi-cloud environments.

    • Company
    • Customers
    • Events
    • Investors
    • Careers Hiring!
    • Partners
    • Press
    • Contact
  • Products
    • Kong Konnect
    • Kong Gateway
    • Kong Mesh
    • Get Started
    • Pricing
  • Resources
    • eBooks
    • Webinars
    • Briefs
    • Blog
    • API Gateway
    • Microservices
  • Open Source
    • Install Kong Gateway
    • Kong Community
    • Kubernetes Ingress
    • Kuma
    • Insomnia
  • Solutions
    • Decentralize
    • Secure & Govern
    • Create a Dev Platform
    • API Gateway
    • Kubernetes
    • Service Mesh
Star
  • Terms•Privacy
© Kong Inc. 2023