AWS
Networking
intermediate
Private-Subnet-Everything App — AWS Architecture Template
Only the ALB is public; app servers, database, and storage all live in private subnets with NAT-only egress.
Why this architecture works
- App instances have no public IPs — the ALB is the sole internet-facing component
- NAT Gateway allows outbound patching and API calls while blocking all unsolicited inbound traffic
- The database accepts connections only from the app tier's security group, not from CIDR ranges
- Secrets Manager access happens over the VPC network, so credentials never transit the public internet
- Security-group references (not IP rules) keep the trust chain intact as instances scale
What's inside (8 resources)
VPC
aws-vpc
Public ALB
aws-alb
NAT Egress
aws-nat-gateway
Private App Servers
aws-ec2
Private Database
aws-rds
App Secrets
aws-secrets-manager
Private Assets
aws-s3
Monitoring
aws-cloudwatch
From template to running infrastructure
- Open this template in the CloudForge visual designer (free account, no credit card).
- Customize resources, names, and connections on the drag-and-drop canvas — or ask Vani, the AI architect, to adapt it.
- Generate production-ready Terraform or CloudFormation in one click.
- Review the plan diff and security scan, then deploy with human approval.