コンテンツにスキップ
Kong Logo | Kong Docs Logo
  • ドキュメント
    • API仕様を確認する
      View all API Specs すべてのAPI仕様を表示 View all API Specs arrow image
    • ドキュメンテーション
      API Specs
      Kong Gateway
      軽量、高速、柔軟なクラウドネイティブAPIゲートウェイ
      Kong Konnect
      SaaSのエンドツーエンド接続のための単一プラットフォーム
      Kong AI Gateway
      GenAI インフラストラクチャ向けマルチ LLM AI Gateway
      Kong Mesh
      Kuma と Envoy をベースにしたエンタープライズサービスメッシュ
      decK
      Kongの構成を宣言型で管理する上で役立ちます
      Kong Ingress Controller
      Kubernetesクラスタ内で動作し、Kongをプロキシトラフィックに設定する
      Kong Gateway Operator
      YAMLマニフェストを使用してKubernetes上のKongデプロイメントを管理する
      Insomnia
      コラボレーティブAPI開発プラットフォーム
  • Plugin Hub
    • Plugin Hubを探索する
      View all plugins すべてのプラグインを表示 View all plugins arrow image
    • 機能性 すべて表示 View all arrow image
      すべてのプラグインを表示
      AI's icon
      AI
      マルチ LLM AI Gatewayプラグインを使用してAIトラフィックを管理、保護、制御する
      認証's icon
      認証
      認証レイヤーでサービスを保護する
      セキュリティ's icon
      セキュリティ
      追加のセキュリティレイヤーでサービスを保護する
      トラフィック制御's icon
      トラフィック制御
      インバウンドおよびアウトバウンドAPIトラフィックの管理、スロットル、制限
      サーバーレス's icon
      サーバーレス
      他のプラグインと組み合わせてサーバーレス関数を呼び出します
      分析と監視's icon
      分析と監視
      APIとマイクロサービストラフィックを視覚化、検査、監視
      変革's icon
      変革
      Kongでリクエストとレスポンスをその場で変換
      ログ記録's icon
      ログ記録
      インフラストラクチャに最適なトランスポートを使用して、リクエストと応答データをログに記録します
  • サポート
  • コミュニティ
  • Kongアカデミー
デモを見る 無料トライアルを開始
Kong Konnect
  • Home icon
  • Kong Konnect
  • Ports and Network Requirements
report-issue問題を報告する
  • Kong Gateway
  • Kong Konnect
  • Kong Mesh
  • Kong AI Gateway
  • Plugin Hub
  • decK
  • Kong Ingress Controller
  • Kong Gateway Operator
  • Insomnia
  • Kuma

  • ドキュメント投稿ガイドライン
  • Introduction
    • Overview of Konnect
    • Architecture
    • Network Resiliency and Availability
    • Port and Network Requirements
    • Private Connections to Other Cloud Providers
      • Create a private connection with AWS PrivateLink
    • Geographic Regions
    • Centralized consumer management
    • Compatibility
    • Stages of Software Availability
    • Release Notes
    • Support
      • Control Plane Upgrades FAQ
      • Supported Installation Options
  • Get Started
    • Overview
    • Add your API
    • Migrating a Self-Managed Kong Gateway into Konnect
  • Gateway Manager
    • Overview
    • Dedicated Cloud Gateways
      • Overview
      • Provision a Dedicated Cloud Gateway
      • Securing Backend Traffic
      • Transit Gateways
      • Azure VNET Peering
      • Custom Domains
      • Custom Plugins
      • Data plane logs
    • Serverless Gateways
      • Overview
      • Provision a serverless Gateway
      • Securing Backend Traffic
      • Custom Domains
    • Data Plane Nodes
      • Installation Options
      • Upgrade a Data Plane Node
      • Verify a Data Plane Node
      • Secure Control Plane/Data Plane Communications
      • Renew Data Plane Certificates
      • Parameter Reference
      • Using Custom DP Labels
    • Control Plane Groups
      • Overview
      • Working with Control Plane Groups
      • Migrate Configuration into Control Plane Groups
      • Conflicts in Control Planes
    • Kong Gateway Configuration in Konnect
      • Overview
      • Manage Plugins
        • Overview
        • Adding Custom Plugins
        • Updating Custom Plugins
        • How to Create Custom Plugins
      • Create Consumer Groups
      • Secrets Management
        • Overview
        • Konnect Config Store
        • Set Up and Use a Vault in Konnect
      • Manage Control Plane Configuration with decK
    • Active Tracing
      • Overview
    • KIC Association
    • Backup and Restore
    • Version Compatibility
    • Troubleshooting
  • Mesh Manager
    • Overview
    • Create a mesh with the Kubernetes demo app
    • Federate a zone control plane to Konnect
    • Migrate a self-managed zone control plane to Konnect
  • Service Catalog
    • Overview
    • Integrations
      • Overview
      • Datadog
      • GitHub
      • GitLab
      • PagerDuty
      • SwaggerHub
      • Traceable
      • Slack
    • Scorecards
  • API Products
    • Overview
    • Product Documentation
    • Productize a Service
  • Dev Portal
    • Overview
    • Dev Portal Configuration Preparation
    • Create a Dev Portal
    • Sign Up for a Dev Portal Account
    • Publish an API to Dev Portal
    • Access and Approval
      • Manage Developer Access
      • Manage Developer Team Access
      • Add Developer Teams from IdPs
      • Manage Application Registrations
      • Configure generic SSO for Dev Portal
      • Configure Okta SSO for Dev Portal
    • Application Lifecycle
    • Register and create an application as a developer
    • Enable and Disable App Registration for API Product Versions
    • Dynamic Client Registration
      • Overview
      • Okta
      • Curity
      • Auth0
      • Azure
      • Custom IdP
    • Portal Management API Automation Guide
    • Audit Logging
      • Overview
      • Set up an Audit Log Webhook
      • Set up an Audit Log Replay Job
    • Portal Customization
      • Overview
      • About Self-Hosted Dev Portal
      • Host your Dev Portal with Netlify
      • Custom Domains
    • Dev Portal SDK
    • Troubleshoot
  • Advanced Analytics
    • Overview
    • Dashboard
    • Explorer
    • Analyze API Usage and Performance with Reports
    • Requests
  • Org Management
    • Plans and Billing
    • Authentication and Authorization
      • Overview
      • Teams
        • Overview
        • Manage Teams
        • Teams Reference
        • Roles Reference
      • Manage Users
      • Manage System Accounts
      • Personal Access Tokens
      • Social Identity Login
      • Org Switcher
      • Configure Generic SSO
      • Configure Okta SSO
      • Login Sessions Reference
      • Troubleshoot
    • Audit Logging
      • Overview
      • Set up an Audit Log Webhook
      • Set up an Audit Log Replay Job
    • Account and Org Deactivation
  • API
    • Overview
    • API Request API (Beta)
      • API Spec
    • API Products API
      • API Spec
    • Audit Logs API
      • API Spec
      • Audit Log Webhooks
    • Control Plane API
      • API Spec
    • Control Plane Configuration API
      • API Spec
    • Cloud Gateways API
      • API Spec
    • Identity API
      • API Spec
      • Identity Integration Guide
      • SSO Customization
    • Konnect Search API (Beta)
      • API Spec
    • Mesh Manager API
      • API Spec
      • Kong Mesh API Reference
    • Portal Client API
      • API Spec
    • Portal Management API
      • API Spec
    • Reference
      • Filtering
      • API Errors
  • Reference
    • Labels
    • Plugin Ordering Reference
    • Konnect Search
    • Terraform Provider
    • Audit Logs
    • Verify audit log signatures
    • IdP SAML attribute mapping
enterprise-switcher-icon 次に切り替える: OSS
On this pageOn this page
  • Control plane ports
  • Data plane node ports
  • Kong Gateway hostnames
    • AU geo
    • EU geo
    • IN geo
    • ME geo
    • US geo
    • Find configuration and telemetry hostnames
  • Kong Ingress Controller hostnames
    • AU geo
    • EU geo
    • IN geo
    • ME geo
    • US geo
    • Find configuration and telemetry hostnames
  • Mesh Manager hostnames

このページは、まだ日本語ではご利用いただけません。翻訳中です。

Ports and Network Requirements

Control plane ports

The Kong Konnect control plane uses the following ports:

Port Protocol Description
443 TCP
HTTPS
Cluster communication port for configuration and telemetry data. The Kong Konnect control plane uses this port to listen for connections and communicate with data plane nodes.
The cluster communication port must be accessible to data plane nodes within the same cluster. This port is protected by mTLS to ensure end-to-end security and integrity.
8071 TCP
UDP
Port used for audit logging.

Kong’s hosted control plane expects traffic on these ports, so they can’t be customized.

Note: If you are unable to make outbound connections using port 443, you can use an existing proxy in your network to make the connection. See Control Plane and Data Plane Communication through a Forward Proxy for details.

Data plane node ports

By default, Kong Gateway listens on the following ports:

Port Protocol Description
8000 HTTP Takes incoming HTTP traffic from consumers, and forwards it to upstream services.
8443 HTTPS Takes incoming HTTPS traffic from consumers, and forwards it to upstream services.

Kong Gateway ports can be fully customized. Set them in kong.conf.

For Kubernetes or Docker deployments, map ports as needed. For example, if you want to use port 3001 for the proxy, map 3001:8000.

Kong Gateway hostnames

Data plane nodes initiate the connection to the Konnect control plane. They require access through firewalls to communicate with the control plane.

To let a data plane node request and receive configuration, and send telemetry data, add the following hostnames to the firewall allowlist (depending on the geographic regions you use).

AU geo

Hostname Description
cloud.konghq.com The Konnect platform.
global.api.konghq.com The Konnect API for platform authentication, identity, permissions, teams, and organizational entitlements and settings.
au.api.konghq.com The Konnect API for the AU geo. Necessary if you are using decK in your workflow, decK uses this API to access and apply configurations.
PORTAL_ID.au.portal.konghq.com The URL for the Dev Portal in the AU geo.
CONTROL_PLANE_DNS_PREFIX.au.cp0.konghq.com Handles configuration for a control plane in the AU geo. Data plane nodes connect to this host to receive configuration updates. This hostname is unique to each organization and control plane.
CONTROL_PLANE_DNS_PREFIX.au.tp0.konghq.com Gathers telemetry data for a control plane in the AU geo. This hostname is unique to each organization and control plane.

EU geo

Hostname Description
cloud.konghq.com The Konnect platform.
global.api.konghq.com The Konnect API for platform authentication, identity, permissions, teams, and organizational entitlements and settings.
eu.api.konghq.com The Konnect API for the EU geo. Necessary if you are using decK in your workflow, decK uses this API to access and apply configurations.
PORTAL_ID.eu.portal.konghq.com The URL for the Dev Portal in the EU geo.
CONTROL_PLANE_DNS_PREFIX.eu.cp0.konghq.com Handles configuration for a control plane in the EU geo. Data plane nodes connect to this host to receive configuration updates. This hostname is unique to each organization and control plane.
CONTROL_PLANE_DNS_PREFIX.eu.tp0.konghq.com Gathers telemetry data for a control plane in the EU geo. This hostname is unique to each organization and control plane.

IN geo

Hostname Description
cloud.konghq.com The Konnect platform.
global.api.konghq.com The Konnect API for platform authentication, identity, permissions, teams, and organizational entitlements and settings.
in.api.konghq.com The Konnect API for the IN geo. Necessary if you are using decK in your workflow, decK uses this API to access and apply configurations.
PORTAL_ID.in.portal.konghq.com The URL for the Dev Portal in the IN geo.
CONTROL_PLANE_DNS_PREFIX.in.cp0.konghq.com Handles configuration for a control plane in the IN geo. Data plane nodes connect to this host to receive configuration updates. This hostname is unique to each organization and control plane.
CONTROL_PLANE_DNS_PREFIX.in.tp0.konghq.com Gathers telemetry data for a control plane in the IN geo. This hostname is unique to each organization and control plane.

ME geo

Hostname Description
cloud.konghq.com The Konnect platform.
global.api.konghq.com The Konnect API for platform authentication, identity, permissions, teams, and organizational entitlements and settings.
me.api.konghq.com The Konnect API for the ME geo. Necessary if you are using decK in your workflow, decK uses this API to access and apply configurations.
PORTAL_ID.me.portal.konghq.com The URL for the Dev Portal in the ME geo.
CONTROL_PLANE_DNS_PREFIX.me.cp0.konghq.com Handles configuration for a control plane in the ME geo. Data plane nodes connect to this host to receive configuration updates. This hostname is unique to each organization and control plane.
CONTROL_PLANE_DNS_PREFIX.me.tp0.konghq.com Gathers telemetry data for a control plane in the ME geo. This hostname is unique to each organization and control plane.

US geo

Hostname Description
cloud.konghq.com The Konnect platform.
global.api.konghq.com The Konnect API for platform authentication, identity, permissions, teams, and organizational entitlements and settings.
us.api.konghq.com The Konnect API for the US geo. Necessary if you are using decK in your workflow, decK uses this API to access and apply configurations.
PORTAL_ID.us.portal.konghq.com The URL for the Dev Portal in the US geo.
CONTROL_PLANE_DNS_PREFIX.us.cp0.konghq.com Handles configuration for a control plane in the US geo. Data plane nodes connect to this host to receive configuration updates. This hostname is unique to each organization and control plane.
CONTROL_PLANE_DNS_PREFIX.us.tp0.konghq.com Gathers telemetry data for a control plane in the US geo. This hostname is unique to each organization and control plane.

Find configuration and telemetry hostnames

You can find the configuration and telemetry hostnames through the Gateway Manager or the Konnect Control Planes API:

Gateway Manager
Control Planes API
  1. Open a control plane.
  2. Select Data Plane Nodes from the side menu, then click the New Data Plane Node button.
  3. Choose the Linux or Kubernetes tab and note the hostnames in the code block for the following parameters:

     cluster_control_plane = example.us.cp0.konghq.com:443
     cluster_server_name = example.us.cp0.konghq.com
     cluster_telemetry_endpoint = example.us.tp0.konghq.com:443
     cluster_telemetry_server_name = example.us.tp0.konghq.com
    
  1. Send a GET request to the control-planes API and inspect the response:

     curl -X GET https://us.api.konghq.com/v2/control-planes/{controlPlaneId}  \
     --header 'Authorization: Bearer <token>'
    

    Tip: You can find your control plane’s API URL on its overview page in the Gateway Manager.

  2. In the response, find your control_plane_endpoint and the telemetry_endpoint:

     {
         "config": {
             "auth_type": "pinned_client_certs",
             "cloud_gateway": false,
             "cluster_type": "CLUSTER_TYPE_CONTROL_PLANE",
             "control_plane_endpoint": "https://example.us.cp0.konghq.com",
             "proxy_urls": [],
             "telemetry_endpoint": "https://example.us.tp0.konghq.com"
         },
         "created_at": "2024-07-24T22:43:31.705Z",
         "description": "",
         "id": "8f0daba0-2246-48fb-8d56-a47ab94saf78",
         "labels": {},
         "name": "Example CP",
         "updated_at": "2024-07-24T22:43:31.705Z"
     }
    

Kong Ingress Controller hostnames

Kong Ingress Controller initiates the connection to the Konnect Control Planes Configuration API to:

  • Synchronize the configuration of the Kong Gateway instances with Konnect
  • Register data plane nodes
  • Fetch license information

Data plane nodes initiate the connection to Konnect APIs to report Analytics data.

Add the following hostnames to the firewall allowlist (depending on the geographic regions you use).

AU geo

Hostname Description
cloud.konghq.com The Konnect platform.
global.api.konghq.com The Konnect API for platform authentication, identity, permissions, teams, and organizational entitlements and settings.
au.api.konghq.com The Konnect API for the AU geo. Necessary if you are using decK in your workflow, decK uses this API to access and apply configurations.
PORTAL_ID.au.portal.konghq.com The URL for the Dev Portal in the AU geo.
CONTROL_PLANE_DNS_PREFIX.au.cp0.konghq.com Handles configuration for a control plane in the AU geo. Data plane nodes connect to this host to receive configuration updates. This hostname is unique to each organization and control plane.
CONTROL_PLANE_DNS_PREFIX.au.tp0.konghq.com Gathers telemetry data for a control plane in the AU geo. This hostname is unique to each organization and control plane.

EU geo

Hostname Description
cloud.konghq.com The Konnect platform.
global.api.konghq.com The Konnect API for platform authentication, identity, permissions, teams, and organizational entitlements and settings.
eu.api.konghq.com The Konnect API for the EU geo. Necessary if you are using decK in your workflow, decK uses this API to access and apply configurations.
PORTAL_ID.eu.portal.konghq.com The URL for the Dev Portal in the EU geo.
CONTROL_PLANE_DNS_PREFIX.eu.cp0.konghq.com Handles configuration for a control plane in the EU geo. Data plane nodes connect to this host to receive configuration updates. This hostname is unique to each organization and control plane.
CONTROL_PLANE_DNS_PREFIX.eu.tp0.konghq.com Gathers telemetry data for a control plane in the EU geo. This hostname is unique to each organization and control plane.

IN geo

Hostname Description
cloud.konghq.com The Konnect platform.
global.api.konghq.com The Konnect API for platform authentication, identity, permissions, teams, and organizational entitlements and settings.
in.api.konghq.com The Konnect API for the IN geo. Necessary if you are using decK in your workflow, decK uses this API to access and apply configurations.
PORTAL_ID.in.portal.konghq.com The URL for the Dev Portal in the IN geo.
CONTROL_PLANE_DNS_PREFIX.in.cp0.konghq.com Handles configuration for a control plane in the IN geo. Data plane nodes connect to this host to receive configuration updates. This hostname is unique to each organization and control plane.
CONTROL_PLANE_DNS_PREFIX.in.tp0.konghq.com Gathers telemetry data for a control plane in the IN geo. This hostname is unique to each organization and control plane.

ME geo

Hostname Description
cloud.konghq.com The Konnect platform.
global.api.konghq.com The Konnect API for platform authentication, identity, permissions, teams, and organizational entitlements and settings.
me.api.konghq.com The Konnect API for the ME geo. Necessary if you are using decK in your workflow, decK uses this API to access and apply configurations.
PORTAL_ID.me.portal.konghq.com The URL for the Dev Portal in the ME geo.
CONTROL_PLANE_DNS_PREFIX.me.cp0.konghq.com Handles configuration for a control plane in the ME geo. Data plane nodes connect to this host to receive configuration updates. This hostname is unique to each organization and control plane.
CONTROL_PLANE_DNS_PREFIX.me.tp0.konghq.com Gathers telemetry data for a control plane in the ME geo. This hostname is unique to each organization and control plane.

US geo

Hostname Description
cloud.konghq.com The Konnect platform.
global.api.konghq.com The Konnect API for platform authentication, identity, permissions, teams, and organizational entitlements and settings.
us.api.konghq.com The Konnect API for the US geo. Necessary if you are using decK in your workflow, decK uses this API to access and apply configurations.
PORTAL_ID.us.portal.konghq.com The URL for the Dev Portal in the US geo.
CONTROL_PLANE_DNS_PREFIX.us.cp0.konghq.com Handles configuration for a control plane in the US geo. Data plane nodes connect to this host to receive configuration updates. This hostname is unique to each organization and control plane.
CONTROL_PLANE_DNS_PREFIX.us.tp0.konghq.com Gathers telemetry data for a control plane in the US geo. This hostname is unique to each organization and control plane.

Find configuration and telemetry hostnames

Gateway Manager
Control Planes API

You can find the telemetry hostname through the Gateway Manager:

  1. Open a control plane.
  2. Click cogwheel icon Control Plane Actions > View Connection Instructions.
  3. Look for the following parameter in the Install the KIC section:

     cluster_telemetry_endpoint: "example.us.tp0.konghq.com:443"
    

You can find the control plane and telemetry hostnames through the Control Planes API.

  1. Send a GET request to the control-planes API and inspect the response:

     curl -X GET https://us.api.konghq.com/v2/control-planes/{controlPlaneId}  \
     --header 'Authorization: Bearer <token>'
    

    Tip: You can find your control plane’s API URL on its overview page in the Gateway Manager.

  2. In the response, find your control_plane_endpoint and the telemetry_endpoint:

     {
         "config": {
             "auth_type": "pinned_client_certs",
             "cloud_gateway": false,
             "cluster_type": "CLUSTER_TYPE_K8S_INGRESS_CONTROLLER",
             "control_plane_endpoint": "https://example.us.cp0.konghq.com",
             "telemetry_endpoint": "https://example.us.tp0.konghq.com"
         },
         "created_at": "2023-03-17T16:54:48.905Z",
         "description": "",
         "id": "32bf6188-906c-483c-b9e3-d7838a089364",
         "labels": {},
         "name": "KIC CP",
         "updated_at": "2024-07-09T07:47:34.514Z"
     }
    

Note: Visit https://ip-addresses.origin.konghq.com/ip-addresses.json for the list of IPs associated to regional hostnames. You can also subscribe to https://ip-addresses.origin.konghq.com/rss for updates.

Mesh Manager hostnames

If you plan to use Mesh Manager to manage your Kong service mesh, you must add the {geo}.mesh.sync.konghq.com:443 hostname to your firewall allowlist. The geo can be au, eu, us, or global.

Thank you for your feedback.
Was this page useful?
情報が多すぎる場合 close cta icon
Kong Konnectを使用すると、より多くの機能とより少ないインフラストラクチャを実現できます。月額1Mリクエストが無料。
無料でお試しください
  • Kong
    APIの世界を動かす

    APIマネジメント、サービスメッシュ、イングレスコントローラーの統合プラットフォームにより、開発者の生産性、セキュリティ、パフォーマンスを大幅に向上します。

    • 製品
      • Kong Konnect
      • Kong Gateway Enterprise
      • Kong Gateway
      • Kong Mesh
      • Kong Ingress Controller
      • Kong Insomnia
      • 製品アップデート
      • 始める
    • ドキュメンテーション
      • Kong Konnectドキュメント
      • Kong Gatewayドキュメント
      • Kong Meshドキュメント
      • Kong Insomniaドキュメント
      • Kong Konnect Plugin Hub
    • オープンソース
      • Kong Gateway
      • Kuma
      • Insomnia
      • Kongコミュニティ
    • 会社概要
      • Kongについて
      • お客様
      • キャリア
      • プレス
      • イベント
      • お問い合わせ
  • 利用規約• プライバシー• 信頼とコンプライアンス
© Kong Inc. 2025