About This Architecture

Reltio AuthNG multi-region routing flow uses NS1 external DNS and AWS Route 53 latency-based routing to direct authentication traffic across US (us-east-1) and EU (eu-west-1) regions. Each region deploys Kong API Gateway in public subnets, routing requests to AuthNG primary and standby instances in private subnets, with RDS databases synchronized across regions. Health checks via Kong trigger CloudWatch alarms, while WAF, IAM, and CloudTrail provide security and compliance monitoring. This architecture demonstrates active-active regional failover with sub-millisecond latency optimization and automated health-driven traffic steering. Fork this diagram to customize VPC CIDR blocks, instance types, or add additional regions for your Reltio deployment.

People also ask

How do you design a multi-region authentication system on AWS with automatic failover and latency optimization?

This diagram shows Reltio AuthNG deployed across US and EU regions with NS1 and Route 53 latency-based routing directing clients to the nearest Kong API Gateway. Each region runs AuthNG primary and standby instances backed by RDS, with health checks triggering CloudWatch alarms for automated failover and cross-region database synchronization ensuring consistency.