AWS three-tier web application
Classic web app on AWS with CloudFront, ALB, ECS Fargate, and RDS Multi-AZ across two availability zones.
The prompt
Three-tier AWS web app architecture. Users hit a CloudFront distribution with WAF, which forwards to an Application Load Balancer in us-east-1. The ALB routes to ECS Fargate tasks running in two private subnets across two availability zones. Tasks read and write to an RDS PostgreSQL Multi-AZ instance and cache in ElastiCache Redis. Static assets are served from S3 via CloudFront. Show the VPC layout with public/private subnets, NAT gateway, internet gateway, route tables, security groups, and IAM task roles. Logs to CloudWatch, traces via X-Ray.
What it generates
A diagram showing the request path from user → CloudFront → ALB → Fargate → RDS, with VPC boundaries, subnets, AZs, observability, and security clearly grouped.
When to use it
When you're building or documenting a standard production web app on AWS and need a starting point that includes networking, security, and observability — not just the compute path.
Generate this diagram in seconds
Copy the prompt above, sign in for free, and paste it into the generator.
Related cloud templates
AWS serverless API
API Gateway + Lambda + DynamoDB with Cognito auth, async processing via SNS/SQS, and full observability.
Azure AKS microservices
Microservices on AKS behind Front Door + Application Gateway with hub-and-spoke networking, Cosmos DB, and Service Bus.
Multi-region active-active deployment
Active-active app spanning two AWS regions with Route 53 latency-based routing, Aurora Global Database, and S3 cross-region replication.