About This Architecture

Multi-AZ enterprise banking architecture spanning eu-west-2 with dual ECS clusters running Fargate On-Demand and Spot instances across two availability zones. Traffic flows through Route 53 and API Gateway to Internal ALBs managing 9 target groups per AZ, with Aurora PostgreSQL Serverless v2 primary-failover databases and cross-region DR to eu-west-1. Security is enforced via KMS encryption, Secrets Manager, STS, CloudTrail audit logging, and private subnets with S3 Gateway Endpoints, while shared services including GitLab, ECR, SNS/SQS, and Tyk API Gateway integrate via Transit Gateway and AWS Direct Connect to on-premises NatWest DC infrastructure. Fork this diagram to customize subnets, add additional regions, or adjust Fargate capacity ratios for your compliance and cost requirements.

People also ask

How do I design a multi-AZ AWS banking architecture with ECS Fargate, Aurora Serverless, and on-premises connectivity via Direct Connect?

This diagram shows a production-grade banking architecture spanning two AZs in eu-west-2 with dual ECS clusters running Fargate On-Demand for high-resource services and Fargate Spot for standard workloads, Aurora PostgreSQL Serverless v2 primary-failover databases, Transit Gateway and Direct Connect for secure on-premises connectivity, and cross-region DR to eu-west-1. Security is enforced through