About This Architecture

AuthNG multi-region Kong failover architecture distributes API gateway traffic across US, EU, and AP regions using AWS Route53 latency-based routing with health checks. Clients resolve through NS1 external DNS to Route53, which routes requests to the nearest Kong gateway (us-east-1, eu-west-1, ap-southeast-1), each backed by Kubernetes clusters running AuthNG services. Each region designates a primary AuthNG target with failover=false, while Kong gateways maintain prioritized failover chains—US→EU→AP, EU→AP→US, AP→EU→US—ensuring service continuity if a regional endpoint fails. This architecture demonstrates active-active regional distribution with intelligent failover, reducing latency for global clients while maintaining high availability across availability zones. Fork and customize this diagram on Diagrams.so to adapt failover priorities, add additional regions, or integrate with your own DNS and load-balancing strategy.

People also ask

How do you design a multi-region Kong API gateway architecture with automatic failover across AWS regions?

This diagram shows a three-region Kong failover setup using AWS Route53 latency-based routing to direct clients to the nearest Kong gateway (US, EU, or AP), with each region running Kubernetes-hosted AuthNG services. Each Kong gateway maintains prioritized failover chains to alternate regions, ensuring requests automatically reroute if the primary target fails, while Route53 health checks continuo