AWS · Enterprise
Enterprise Multi-Tier Cloud Architecture
Full-stack AWS architecture featuring CloudFront CDN, API Gateway, nested VPC/Subnets, ECS tasks, ElastiCache, and RDS Proxy. This diagram is written in ArchLex and passes AWS provider checks.
Diagram and source
provider aws
direction LR
validation normal
account enterprise-prod {
region us-east-1 {
dns: route53
cdn: cloudfront
apigw: api-gateway
cache: elasticache
db_nosql: dynamodb
dns > cdn > apigw
vpc production-vpc {
subnet public-subnet-1 {
ingress: alb
}
subnet private-subnet-a {
web_app: ecs
proxy: rds-proxy
db_sql: rds
}
}
apigw > ingress > web_app
web_app > cache
web_app > proxy > db_sql
apigw > db_nosql
}
}What is in this diagram.
Resources
- dns Amazon Route 53
- cdn Amazon CloudFront
- apigw Amazon API Gateway
- cache Amazon ElastiCache
- db_nosql Amazon DynamoDB
- ingress Application Load Balancer
- web_app Amazon ECS
- proxy Amazon RDS Proxy
- db_sql Amazon RDS
Relationships
- dns connects cdn
- cdn connects apigw
- apigw connects ingress
- ingress connects web_app
- web_app connects cache
- web_app connects proxy
- proxy connects db_sql
- apigw connects db_nosql
Boundaries
- account enterprise-prod
- region us-east-1
- vpc production-vpc
- subnet public-subnet-1
- subnet private-subnet-a
Render it yourself.
Save the source as enterprise-cloud.arch and render it with the CLI, or ask your agent to adapt it through the ArchLex MCP server.
npx @archlex/cli render enterprise-cloud.arch --output enterprise-cloud.svgRelated examples.
- Minimal Vertical SliceRDS Proxy, RDS Database, and ECS Service
- Display Labels & Named InstancesInstance names and custom display labels distinguishing primary and replica databases
- Classic 3-Tier Web ArchitectureApplication Load Balancer distributing to ECS container tasks connected to RDS
- Serverless MicroserviceAPI Gateway invoking Lambda function accessing DynamoDB table