AWS
AWS Three-Tier Web Application
This AWS architecture diagram separates a public web application into edge, web, application and data tiers. Internet traffic reaches Amazon CloudFront, then an Application Load Balancer and an EC2 web tier. The web tier calls an EC2 application tier, which stores relational data in Amazon RDS and files in Amazon S3. The drawing gives teams a compact way to discuss traffic flow and responsibility boundaries before adding more detailed networking controls.
Make this diagram your own.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
CASE ANALYSIS
Scenario
A public AWS web application.
Key decisions
- Edge delivery: CloudFront receives public HTTPS requests.
- Traffic distribution: The Application Load Balancer routes requests to the web tier.
- Separated data: The application tier uses RDS and S3 for different storage needs.
When to reuse this
Use this as a simple three-tier starting point for an AWS web application.
FAQ
Frequently asked questions
What are the three tiers?
The web tier receives requests, the application tier runs application logic, and the data tier stores application data.
Why place CloudFront at the edge?
CloudFront receives public web requests before they continue to the application load balancer.
What storage services are shown?
The example uses Amazon RDS for relational data and Amazon S3 for files.
Open this example in the editor →
Tweak it with chat, export PNG/SVG, or fork it for your own use case.
network-aws-three-tier-web-application