What is Kong Gateway?

Kong Gateway, managed via Kong Konnect, provides the unified entry point for both Public (internet-facing) and Private (internal/VPN) API endpoints.

Architecture Roles

Kong as the Modern Ingress: In the "Orbit Product Account," Kong is positioned at the EKS Ingress level. It receives traffic from the Load Balancers (NLB/ALB) and routes it to specific Kubernetes services (Stateless/Stateful Managed Node Groups).
Public Exposure: For internet-facing services and vehicle traffic arriving via the Internet Gateway, Kong handles the Public API HTTPS traffic. It provides a secure "front door" for external consumers to access our APIs.
Private Exposure: For internal traffic arriving from the Transit VPC (via Direct Connect), Kong manages the Private API endpoints. This allows secure, authenticated communication between the data center and our internal AI tools without exposing them to the open web.
Kong Konnect (SaaS Management): Konnect acts as the global Control Plane. It allows our platform team to manage these gateway runtimes, deploy plugins (like JWT Auth or Rate Limiting), and monitor API health from a centralized cloud interface, regardless of which VPC the traffic is in.

Explore the sections above to know more about the API gateway platform.