About This Architecture

Multi-tier WAS architecture spanning two AWS availability zones with an Application Load Balancer distributing traffic across four WAS application instances in the public subnet. Application tier instances (prdsmtwas01-04) route requests to dedicated worker and batch processing tiers in private subnets, each protected by security groups enforcing least-privilege access. The topology demonstrates high availability and fault isolation across AZ-1 and AZ-2 within the prd-smt-vpc, with separate security groups controlling traffic between application, worker, and batch tiers. Fork this diagram to customize security group rules, add RDS backends, or scale worker instances based on your workload demands.

People also ask

How do I design a multi-tier WAS application architecture on AWS with load balancing and worker processing across availability zones?

This diagram shows a production WAS architecture using an Application Load Balancer to distribute traffic across four application instances (prdsmtwas01-04) in a public subnet, with dedicated worker and batch processing tiers in private subnets protected by security groups. The design spans AZ-1 and AZ-2 for high availability, with security group rules enforcing least-privilege communication betwe