About This Architecture

Highly available web architecture for a university student records application spanning two availability zones in AWS us-east-1 with auto-scaled Node.js web servers behind an Application Load Balancer. Internet users connect via HTTP to the ALB, which distributes traffic across EC2 instances in public subnets across AZ-1a and AZ-1b, each running Node.js on t3.micro instances managed by an Auto Scaling Group with min:2, desired:2, max:4 capacity. The architecture isolates a MySQL 8.0 RDS database in private subnets with no internet access, secured by restrictive security groups that allow inbound MySQL 3306 only from web server security groups. Secrets Manager stores database credentials, CloudWatch monitors CPU utilization with alarms triggering ASG scaling, and a Cloud9 instance provides CLI access for testing and migration tasks. This design demonstrates AWS best practices for availability, security isolation, and operational resilience. Fork and customize this diagram on Diagrams.so to adapt it for your institution's enrollment scale and compliance requirements.

People also ask

How do I design a highly available AWS web application across multiple availability zones with auto-scaling and database security?

This diagram shows a production-ready pattern: place internet-facing ALB in public subnets across AZ-1a and AZ-1b, auto-scale Node.js EC2 instances (min:2, max:4) behind it, isolate RDS MySQL in private subnets with security groups allowing inbound 3306 only from web servers, and use Secrets Manager for credentials. CloudWatch CPU alarms trigger ASG scaling to handle demand while maintaining avail