Geographic Regions

Kong Konnect allows you to host and operate your cloud instance in a geographic region that you specify. This is important for data privacy and regulatory compliance for you organization.

Geographic regions allow you to also operate Kong Konnect in a similar geo to your users and their infrastructure applications.

Supported geos

Control planes

Kong Konnect currently supports the following geos:

Dedicated Cloud Gateways

AWS

Azure

Kong Konnect Dedicated Cloud Gateways support the following AWS geos:

North America:
- Ohio (us-east-2)
- Oregon (us-west-2)
- California, USA (us-west-1)
- Montreal (ca-central-1)
Europe:
- Frankfurt (eu-central-1)
- Ireland (eu-west-1)
- London (eu-west-2)
- Paris (eu-west-3)
- Zurich (eu-central-2)
Asia Pacific:
- Tokyo (ap-northeast-1)
- Singapore (ap-southeast-1)
- Sydney (ap-southeast-2)
- Mumbai (ap-south-1)
- Hyderabad (ap-south-2)
- Seoul (ap-northeast-2)
- Jakarta (ap-southeast-3)
Middle East, and Africa
- United Arab Emirates (me-central-1)

Kong Konnect Dedicated Cloud Gateways support the following Azure geos:

North America:
- Virginia (eastus2)
- Washington (westus2)
Europe:
- Frankfurt (germanywestcentral)
- Ireland (northeurope)
- UK South (uksouth)

Geo management

When you create a Kong Konnect account, you select a geographic region for your instance. Geos are distinct deployments of Konnect with objects, such as services and consumers, that are geo-specific. Only authentication, billing, and usage is shared between Konnect geos.

The following objects are geo-specific and are not shared between geos: