Load balancer
HTTPS listener with an ACM certificate. Plain HTTP is redirected.
/health always answers without the databaseLive on AWS · ap-south-1
Highly available web app on AWS
Two Availability Zones, private subnets and TLS end to end. Built with Terraform, shipped by GitHub Actions, and served by whichever healthy instance the load balancer picks.
This request was served by
i-07592d0cc693868fa
ap-south-1a
Request path
The highlighted instance is the one answering you right now.
You
HTTPS, TLS 1.3
Public subnets
Application Load Balancer
ACM certificate, HTTP to HTTPS
Private subnetap-south-1ai-07592d0cc693868fa
Private subnetsecond zonediscovering
Database subnets
RDS MySQL
TLS required, encrypted
VPC endpoint
Amazon S3
uploads and ALB logs
Live checks
Run on this instance for this request.
Database
MySQL 8.0.46-eol-2-rds.20260908, reached over a verified TLS connection.
cipher TLS_AES_256_GCM_SHA384Object storage
Wrote an object to S3 and read it back through the VPC endpoint.
uploads/healthcheck/i-07592d0cc693868fa.txtRelease
Rolled out by an instance refresh that keeps half the fleet serving.
version f01eb919f94bLoad balancing, live
Send a burst of requests from your browser and watch them spread across zones.
Nothing sent yet.
Visits recorded in MySQL
Every page view and burst request is written to the database by the instance that served it.
68total
Built in
What keeps it safe and running.
- Instances and database in private subnets
- No SSH, Session Manager only
- IMDSv2 required
- Database password in Secrets Manager
- Least-privilege IAM
- Encryption at rest everywhere
- GitHub OIDC, no stored AWS keys
- Auto Scaling on CPU, 2 to 4 instances
- CloudWatch alarms to SNS
- Strict security headers and CSP