Skip to content
Kong Logo | Kong Docs Logo
  • Docs
    • Explore the API Specs
      View all API Specs View all API Specs View all API Specs arrow image
    • Documentation
      API Specs
      Kong Gateway
      Lightweight, fast, and flexible cloud-native API gateway
      Kong Konnect
      Single platform for SaaS end-to-end connectivity
      Kong AI Gateway
      Multi-LLM AI Gateway for GenAI infrastructure
      Kong Mesh
      Enterprise service mesh based on Kuma and Envoy
      decK
      Helps manage Kong’s configuration in a declarative fashion
      Kong Ingress Controller
      Works inside a Kubernetes cluster and configures Kong to proxy traffic
      Kong Gateway Operator
      Manage your Kong deployments on Kubernetes using YAML Manifests
      Insomnia
      Collaborative API development platform
  • Plugin Hub
    • Explore the Plugin Hub
      View all plugins View all plugins View all plugins arrow image
    • Functionality View all View all arrow image
      View all plugins
      AI's icon
      AI
      Govern, secure, and control AI traffic with multi-LLM AI Gateway plugins
      Authentication's icon
      Authentication
      Protect your services with an authentication layer
      Security's icon
      Security
      Protect your services with additional security layer
      Traffic Control's icon
      Traffic Control
      Manage, throttle and restrict inbound and outbound API traffic
      Serverless's icon
      Serverless
      Invoke serverless functions in combination with other plugins
      Analytics & Monitoring's icon
      Analytics & Monitoring
      Visualize, inspect and monitor APIs and microservices traffic
      Transformations's icon
      Transformations
      Transform request and responses on the fly on Kong
      Logging's icon
      Logging
      Log request and response data using the best transport for your infrastructure
  • Support
  • Community
  • Kong Academy
Get a Demo Start Free Trial
Kong Konnect
  • Home icon
  • Kong Konnect
  • Private Connections
  • Create a private connection with AWS PrivateLink
github-edit-pageEdit this page
report-issueReport an issue
  • Kong Gateway
  • Kong Konnect
  • Kong Mesh
  • Kong AI Gateway
  • Plugin Hub
  • decK
  • Kong Ingress Controller
  • Kong Gateway Operator
  • Insomnia
  • Kuma

  • Docs contribution guidelines
  • 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 Switch to OSS
On this pageOn this page
  • Prerequisites
  • Steps

Create a private connection with AWS PrivateLink

Connect your data plane to your Konnect control plane or make Konnect API calls (including Admin API calls for control plane configuration) with a private connection to stay compliant and save data transfer costs

You can establish a private connection to ensure that the data transmitted between Konnect and your AWS environment is secure. This private connection uses AWS PrivateLink and is available for the following AWS regions:

  • us-east-2
  • us-west-2
  • eu-central-1
  • eu-west-1
  • eu-west-2
  • ap-southeast-1
  • ap-southeast-2

If you want to create a connection with a different AWS region, contact Kong Support.

Prerequisites

Create a VPC, subnets, and a security group in AWS. For more information, see the AWS documentation.

Steps

Control Plane <> Data Plane Communication
Konnect Admin API
  1. In the AWS Console, connect to your data plane region, open the Endpoints section of the VPC dashboard and create a new endpoint.

  2. Enter a name tag for the endpoint that includes the Konnect control plane geo that you want to connect to. For example: konnect-us-geo.

  3. Select the Endpoint services that use NLBs and GWLBs service category.

  4. Find the correct service name for your region in the tables below. Open the tab that matches your AWS region and use the PrivateLink service name for your Konnect geo. For example, com.amazonaws.vpce.us-east-2.vpce-svc-096fe7ba54ebc32db for the us-east-2 AWS region and US Konnect geo.

    ap-southeast-1
    ap-southeast-2
    eu-central-1
    eu-west-1
    eu-west-2
    us-east-2
    us-west-2
    Konnect Geographical Region PrivateLink service name Private DNS name
    AP com.amazonaws.vpce.ap-southeast-1.vpce-svc-08f76d27d29b02a09 ap.svc.konghq.com
    EU com.amazonaws.vpce.ap-southeast-1.vpce-svc-0a04604ecaed18457 eu.svc.konghq.com
    GLOBAL com.amazonaws.vpce.ap-southeast-1.vpce-svc-0b1da0ec96942fdb0 global.svc.konghq.com
    IN com.amazonaws.vpce.ap-southeast-1.vpce-svc-0c6699c89ac27323c in.svc.konghq.com
    ME com.amazonaws.vpce.ap-southeast-1.vpce-svc-00689717c9085d08a me.svc.konghq.com
    US com.amazonaws.vpce.ap-southeast-1.vpce-svc-0eeaa22ed2d6268eb us.svc.konghq.com
    Konnect Geographical Region PrivateLink service name Private DNS name
    AP com.amazonaws.vpce.ap-southeast-2.vpce-svc-055ba6ff5a3f551c9 ap.svc.konghq.com
    EU com.amazonaws.vpce.ap-southeast-2.vpce-svc-02a339e8dc8ec72c6 eu.svc.konghq.com
    GLOBAL com.amazonaws.vpce.ap-southeast-2.vpce-svc-0dddc28f5f8b68cbc global.svc.konghq.com
    IN com.amazonaws.vpce.ap-southeast-2.vpce-svc-050ea149424be6d3c in.svc.konghq.com
    ME com.amazonaws.vpce.ap-southeast-2.vpce-svc-008f231c7501e72c2 me.svc.konghq.com
    US com.amazonaws.vpce.ap-southeast-2.vpce-svc-0600dd84f39e7b12a us.svc.konghq.com
    Konnect Geographical Region PrivateLink service name Private DNS name
    AP com.amazonaws.vpce.eu-central-1.vpce-svc-0c3f0574080bdd859 ap.svc.konghq.com
    EU com.amazonaws.vpce.eu-central-1.vpce-svc-05e6822fbce58e1a0 eu.svc.konghq.com
    GLOBAL com.amazonaws.vpce.eu-central-1.vpce-svc-050c17c4f2970705f global.svc.konghq.com
    IN com.amazonaws.vpce.eu-central-1.vpce-svc-0a5c165336502e526 in.svc.konghq.com
    ME com.amazonaws.vpce.eu-central-1.vpce-svc-0e6497e6df9928a80 me.svc.konghq.com
    US com.amazonaws.vpce.eu-central-1.vpce-svc-01d3dd232e277feeb us.svc.konghq.com
    Konnect Geographical Region PrivateLink service name Private DNS name
    AP com.amazonaws.vpce.eu-west-1.vpce-svc-08edf59f8bc1d2262 ap.svc.konghq.com
    EU com.amazonaws.vpce.eu-west-1.vpce-svc-037bd988d9a9d4e3a eu.svc.konghq.com
    GLOBAL com.amazonaws.vpce.eu-west-1.vpce-svc-0852df4643d76b28e global.svc.konghq.com
    IN com.amazonaws.vpce.eu-west-1.vpce-svc-029c2f6bedf7c346f in.svc.konghq.com
    ME com.amazonaws.vpce.eu-west-1.vpce-svc-0978fbaf50bfc67d9 me.svc.konghq.com
    US com.amazonaws.vpce.eu-west-1.vpce-svc-01070d7c2137e0ee1 us.svc.konghq.com
    Konnect Geographical Region PrivateLink service name Private DNS name
    AP com.amazonaws.vpce.eu-west-2.vpce-svc-0500cb14757738225 ap.svc.konghq.com
    EU com.amazonaws.vpce.eu-west-2.vpce-svc-0b2d5879e15254e35 eu.svc.konghq.com
    GLOBAL com.amazonaws.vpce.eu-west-2.vpce-svc-06dfcb0204806e836 global.svc.konghq.com
    IN com.amazonaws.vpce.eu-west-2.vpce-svc-08e51a56a0ee549c6 in.svc.konghq.com
    ME com.amazonaws.vpce.eu-west-2.vpce-svc-0ab99eeae8121c7d8 me.svc.konghq.com
    US com.amazonaws.vpce.eu-west-2.vpce-svc-0c23345bb2ef7b298 us.svc.konghq.com
    Konnect Geographical Region PrivateLink service name Private DNS name
    AP com.amazonaws.vpce.us-east-2.vpce-svc-03da89378358921bc ap.svc.konghq.com
    EU com.amazonaws.vpce.us-east-2.vpce-svc-0cb28c923823735ac eu.svc.konghq.com
    GLOBAL com.amazonaws.vpce.us-east-2.vpce-svc-0b6f58f5e17620d89 global.svc.konghq.com
    IN com.amazonaws.vpce.us-east-2.vpce-svc-0b439785c0b06bb97 in.svc.konghq.com
    ME com.amazonaws.vpce.us-east-2.vpce-svc-0f1c86fb6399d4fe5 me.svc.konghq.com
    US com.amazonaws.vpce.us-east-2.vpce-svc-096fe7ba54ebc32db us.svc.konghq.com
    Konnect Geographical Region PrivateLink service name Private DNS name
    AP com.amazonaws.vpce.us-west-2.vpce-svc-078156c9cc9048988 ap.svc.konghq.com
    EU com.amazonaws.vpce.us-west-2.vpce-svc-0e03b7c33104a4a4f eu.svc.konghq.com
    GLOBAL com.amazonaws.vpce.us-west-2.vpce-svc-053325dfb74719cb9 global.svc.konghq.com
    IN com.amazonaws.vpce.us-west-2.vpce-svc-0865c535fc28a3060 in.svc.konghq.com
    ME com.amazonaws.vpce.us-west-2.vpce-svc-0fce4d5504650e9a3 me.svc.konghq.com
    US com.amazonaws.vpce.us-west-2.vpce-svc-0d2994122fea007ca us.svc.konghq.com
  5. Verify the service. If the service name can’t be verified, contact Kong Support.

  6. Once the service name is verified, select the VPC, subnets, and security groups to associate with this endpoint. Make sure that:
    • The security group accepts inbound traffic on TCP port 443.
    • The DNS name parameter in the additional settings is enabled.
  7. Create the VPC endpoint and wait for its status to change to available. We recommend waiting for 10 minutes before using it.

  8. Update your data plane configuration to connect to the control plane through the private connection. Use the private DNS name that matches your control plane geo in the tables above. For the US Konnect geo, the updated Kong data plane configuration in kong.conf looks like this:
    cluster_control_plane = us.svc.konghq.com/cp/{cluster_prefix}
    cluster_server_name = us.svc.konghq.com
    cluster_telemetry_endpoint = us.svc.konghq.com:443/tp/{cluster_prefix}
    cluster_telemetry_server_name = us.svc.konghq.com
    
  1. In the AWS Console, connect to region from where Konnect API calls would be made, open the Endpoints section of the VPC dashboard and create a new endpoint.

  2. Enter a name tag for the endpoint that includes the Konnect control plane region that you want to connect to. For example: konnect-us-region.

  3. Select the Endpoint services that use NLBs and GWLBs service category.

  4. Find the correct service name for your region in the tables below. Open the tab that matches your AWS region and use the PrivateLink service name for your Konnect geo. For example, com.amazonaws.vpce.us-east-2.vpce-svc-096fe7ba54ebc32db for the us-east-2 AWS region and US Konnect region.

    ap-southeast-1
    ap-southeast-2
    eu-central-1
    eu-west-1
    eu-west-2
    us-east-2
    us-west-2
    Konnect Geographical Region PrivateLink service name Private DNS name
    AP com.amazonaws.vpce.ap-southeast-1.vpce-svc-08f76d27d29b02a09 ap.svc.konghq.com
    EU com.amazonaws.vpce.ap-southeast-1.vpce-svc-0a04604ecaed18457 eu.svc.konghq.com
    GLOBAL com.amazonaws.vpce.ap-southeast-1.vpce-svc-0b1da0ec96942fdb0 global.svc.konghq.com
    IN com.amazonaws.vpce.ap-southeast-1.vpce-svc-0c6699c89ac27323c in.svc.konghq.com
    ME com.amazonaws.vpce.ap-southeast-1.vpce-svc-00689717c9085d08a me.svc.konghq.com
    US com.amazonaws.vpce.ap-southeast-1.vpce-svc-0eeaa22ed2d6268eb us.svc.konghq.com
    Konnect Geographical Region PrivateLink service name Private DNS name
    AP com.amazonaws.vpce.ap-southeast-2.vpce-svc-055ba6ff5a3f551c9 ap.svc.konghq.com
    EU com.amazonaws.vpce.ap-southeast-2.vpce-svc-02a339e8dc8ec72c6 eu.svc.konghq.com
    GLOBAL com.amazonaws.vpce.ap-southeast-2.vpce-svc-0dddc28f5f8b68cbc global.svc.konghq.com
    IN com.amazonaws.vpce.ap-southeast-2.vpce-svc-050ea149424be6d3c in.svc.konghq.com
    ME com.amazonaws.vpce.ap-southeast-2.vpce-svc-008f231c7501e72c2 me.svc.konghq.com
    US com.amazonaws.vpce.ap-southeast-2.vpce-svc-0600dd84f39e7b12a us.svc.konghq.com
    Konnect Geographical Region PrivateLink service name Private DNS name
    AP com.amazonaws.vpce.eu-central-1.vpce-svc-0c3f0574080bdd859 ap.svc.konghq.com
    EU com.amazonaws.vpce.eu-central-1.vpce-svc-05e6822fbce58e1a0 eu.svc.konghq.com
    GLOBAL com.amazonaws.vpce.eu-central-1.vpce-svc-050c17c4f2970705f global.svc.konghq.com
    IN com.amazonaws.vpce.eu-central-1.vpce-svc-0a5c165336502e526 in.svc.konghq.com
    ME com.amazonaws.vpce.eu-central-1.vpce-svc-0e6497e6df9928a80 me.svc.konghq.com
    US com.amazonaws.vpce.eu-central-1.vpce-svc-01d3dd232e277feeb us.svc.konghq.com
    Konnect Geographical Region PrivateLink service name Private DNS name
    AP com.amazonaws.vpce.eu-west-1.vpce-svc-08edf59f8bc1d2262 ap.svc.konghq.com
    EU com.amazonaws.vpce.eu-west-1.vpce-svc-037bd988d9a9d4e3a eu.svc.konghq.com
    GLOBAL com.amazonaws.vpce.eu-west-1.vpce-svc-0852df4643d76b28e global.svc.konghq.com
    IN com.amazonaws.vpce.eu-west-1.vpce-svc-029c2f6bedf7c346f in.svc.konghq.com
    ME com.amazonaws.vpce.eu-west-1.vpce-svc-0978fbaf50bfc67d9 me.svc.konghq.com
    US com.amazonaws.vpce.eu-west-1.vpce-svc-01070d7c2137e0ee1 us.svc.konghq.com
    Konnect Geographical Region PrivateLink service name Private DNS name
    AP com.amazonaws.vpce.eu-west-2.vpce-svc-0500cb14757738225 ap.svc.konghq.com
    EU com.amazonaws.vpce.eu-west-2.vpce-svc-0b2d5879e15254e35 eu.svc.konghq.com
    GLOBAL com.amazonaws.vpce.eu-west-2.vpce-svc-06dfcb0204806e836 global.svc.konghq.com
    IN com.amazonaws.vpce.eu-west-2.vpce-svc-08e51a56a0ee549c6 in.svc.konghq.com
    ME com.amazonaws.vpce.eu-west-2.vpce-svc-0ab99eeae8121c7d8 me.svc.konghq.com
    US com.amazonaws.vpce.eu-west-2.vpce-svc-0c23345bb2ef7b298 us.svc.konghq.com
    Konnect Geographical Region PrivateLink service name Private DNS name
    AP com.amazonaws.vpce.us-east-2.vpce-svc-03da89378358921bc ap.svc.konghq.com
    EU com.amazonaws.vpce.us-east-2.vpce-svc-0cb28c923823735ac eu.svc.konghq.com
    GLOBAL com.amazonaws.vpce.us-east-2.vpce-svc-0b6f58f5e17620d89 global.svc.konghq.com
    IN com.amazonaws.vpce.us-east-2.vpce-svc-0b439785c0b06bb97 in.svc.konghq.com
    ME com.amazonaws.vpce.us-east-2.vpce-svc-0f1c86fb6399d4fe5 me.svc.konghq.com
    US com.amazonaws.vpce.us-east-2.vpce-svc-096fe7ba54ebc32db us.svc.konghq.com
    Konnect Geographical Region PrivateLink service name Private DNS name
    AP com.amazonaws.vpce.us-west-2.vpce-svc-078156c9cc9048988 ap.svc.konghq.com
    EU com.amazonaws.vpce.us-west-2.vpce-svc-0e03b7c33104a4a4f eu.svc.konghq.com
    GLOBAL com.amazonaws.vpce.us-west-2.vpce-svc-053325dfb74719cb9 global.svc.konghq.com
    IN com.amazonaws.vpce.us-west-2.vpce-svc-0865c535fc28a3060 in.svc.konghq.com
    ME com.amazonaws.vpce.us-west-2.vpce-svc-0fce4d5504650e9a3 me.svc.konghq.com
    US com.amazonaws.vpce.us-west-2.vpce-svc-0d2994122fea007ca us.svc.konghq.com
  5. Verify the service. If the service name can’t be verified, contact Kong Support.

  6. Once the service name is verified, select the VPC, subnets, and security groups to associate with this endpoint. Make sure that:
    • The security group accepts inbound traffic on TCP port 443.
    • The DNS name parameter in the additional settings is enabled.
  7. Create the VPC endpoint and wait for its status to change to available. We recommend waiting for 10 minutes before using it.

  8. Repeat steps 1-7 for GLOBAL Konnect geographical region to make Global API requests.

  9. Konnect Admin API requests or decK commands from dataplane nodes can be made now. Konnect API requests for other regional entities such as Portal can also be made now.
Thank you for your feedback.
Was this page useful?
Too much on your plate? close cta icon
More features, less infrastructure with Kong Konnect. 1M requests per month for free.
Try it for Free
  • Kong
    Powering the API world

    Increase developer productivity, security, and performance at scale with the unified platform for API management, service mesh, and ingress controller.

    • Products
      • Kong Konnect
      • Kong Gateway Enterprise
      • Kong Gateway
      • Kong Mesh
      • Kong Ingress Controller
      • Kong Insomnia
      • Product Updates
      • Get Started
    • Documentation
      • Kong Konnect Docs
      • Kong Gateway Docs
      • Kong Mesh Docs
      • Kong Insomnia Docs
      • Kong Konnect Plugin Hub
    • Open Source
      • Kong Gateway
      • Kuma
      • Insomnia
      • Kong Community
    • Company
      • About Kong
      • Customers
      • Careers
      • Press
      • Events
      • Contact
  • Terms• Privacy• Trust and Compliance
© Kong Inc. 2025