About This Architecture

CloudShare pre-production architecture spans AWS us-east-1 and on-premises datacenters, integrating EKS with hybrid workloads via VPN. The VPC (10.32.0.0/16) hosts an EKS cluster (k8s 1.34) across two AZs with Karpenter auto-scaling, managed by ArgoCD, running microservices including Command Worker, Marketplace, Webhooks, and backend services. Data flows through SQS queues, ElastiCache Redis, three SQL Server RDS instances, and Route53 private zones with resolver forwarding to on-premises DNS (10.13.0.0/16, 10.113.0.0/16, 10.213.0.0/16, 10.214.0.0). This hybrid topology demonstrates multi-AZ resilience, IRSA-based least-privilege access, and secure VPN connectivity for distributed teams and legacy system integration. Fork this diagram on Diagrams.so to customize subnets, add additional services, or adapt for your own hybrid cloud strategy. The migration status indicators show phased rollout progress across infrastructure components.

People also ask

How do you design a hybrid AWS EKS pre-production environment that securely connects to on-premises datacenters?

This diagram shows a production-ready hybrid topology: EKS cluster across two us-east-1 AZs with Karpenter spot/on-demand scaling, ArgoCD-managed microservices, RDS SQL Server instances, ElastiCache Redis, and VPN Gateway tunneling to on-premises networks (10.13.0.0/16, 10.113.0.0/16, 10.213.0.0/16, 10.214.0.0). Route53 private zones and resolver forwarding enable seamless DNS resolution between A