Dedicated Cloud Gateway | API Request Flow

Dedicated Cloud Gateway | API Request Flow An architecture diagram generated by Archify. Internal Control Plane · Internal API configuration · Konnect | North America (US geo) | 2 CPs Internal Control Plane Internal API configuration Public Control Plane · Selected public API configuration · Konnect | North America (US geo) | 2 CPs Public Control Plane Selected public API configuration App A · Internal API consumer · Provider A VPC | Account A | Tokyo App A Internal API consumer Private DCGW DP pool · Private ingress | Tokyo · Kong-managed VPC | Tokyo | Private ingress Private DCGW DP pool Private ingress | Tokyo Public DCGW DP pool · Public ingress | Tokyo · Kong-managed VPC | Tokyo | Public ingress Public DCGW DP pool Public ingress | Tokyo External App · Approved public APIs only · Architecture component External App Approved public APIs only App B · Private upstream APIs · Provider B VPC | Account B | Tokyo App B Private upstream APIs App C · Private upstream for selected APIs · Provider C VPC | Account C | Tokyo App C Private upstream for selected APIs Private HTTPS via TGW Private upstream via TGW Internal APIs via TGW Internet HTTPS Private upstream via TGW DP-initiated management channel DP-initiated management channel Konnect | North America (US geo) | 2 CPs Kong-managed VPC | Tokyo | Private ingress Kong-managed VPC | Tokyo | Public ingress Provider A VPC | Account A | Tokyo Provider B VPC | Account B | Tokyo Provider C VPC | Account C | Tokyo

Internal API path

  • • App A → Private-ingress DCGW → App B / C via TGW.
  • • api_access: private. No direct Internet ingress.

Public API, private upstream

  • • External App → Public-ingress DCGW → App C via TGW.
  • • api_access: public. App C has no Internet-facing endpoint.

Separate exposure from connectivity

  • • Both DCGW VPCs attach to TGW; route tables restrict reachability.
  • • Separate CP/DP deployments keep internal routes off public ingress.