Create an AWS Architecture Diagram

What you'll build

In this tutorial, you will design a production-ready AWS cloud architecture diagram featuring:

• Edge networking: Route 53 DNS and CloudFront CDN distribution.
• Public DMZ: Application Load Balancer (ALB) and NAT Gateways.
• Private Compute Tier: ECS Fargate container clusters running across multiple Availability Zones.
• Private Data Tier: Amazon Aurora PostgreSQL Multi-AZ cluster and Amazon ElastiCache.
• Storage: Amazon S3 bucket for static assets and file uploads.

Before you start

• Open a blank canvas in Rekhic or inspect the Production AWS Architecture blueprint in the Templates Catalog.

Step 1: Place Edge and DNS Services

1. Drop an Architecture Node (A) at the top center. Label it Amazon Route 53, icon Route 53.
2. Drop another node directly beneath it. Label it Amazon CloudFront, icon CloudFront.
3. To the right of CloudFront, drop an S3 bucket node: Label Amazon S3 (Static Web Assets), icon S3.
4. Connect Route 53 to CloudFront (DNS resolution).
5. Connect CloudFront to Amazon S3 (Origin: Static Assets / S3 OAC).

Step 2: Establish the VPC and Public Subnet Tier

1. Select the Rectangle tool (R) and draw a large container for your VPC. Label it AWS VPC (us-east-1) - 10.0.0.0/16. Set stroke to dashed and send to back (Cmd/Ctrl + Shift + [).
2. Inside the VPC, near the top, draw a smaller boundary labeled Public Subnets (Multi-AZ).
3. Inside the Public Subnets container, place an Architecture Node: Label Application Load Balancer, icon ALB.
4. Connect CloudFront to Application Load Balancer (Origin: Dynamic API Traffic).

Step 3: Configure Private Application Subnets (Compute)

1. Beneath the public subnets, draw a boundary container labeled Private App Subnets (AZ-a / AZ-b).
2. Inside, place two architecture nodes representing container tasks:
   • Left node: Label ECS Fargate Task (AZ-1a), icon ECS.
   • Right node: Label ECS Fargate Task (AZ-1b), icon ECS.
3. Connect Application Load Balancer to both ECS tasks with arrows labeled Target Group: HTTP :8080.

Step 4: Configure the Private Database Tier

1. Beneath the compute tier, draw a boundary container labeled Private Isolated Database Subnets.
2. Place two data store nodes using the Ellipse tool (O) or Architecture Node tool:
   • Primary: Label Amazon Aurora PostgreSQL (Primary Writer), icon RDS.
   • Replica: Label Amazon Aurora PostgreSQL (Read Replica), icon RDS.
   • Cache: Label Amazon ElastiCache (Redis Cluster), icon ElastiCache.
3. Connect the ECS tasks to the Aurora primary database (SQL write) and read replica (SQL read).
4. Connect the ECS tasks to the ElastiCache cluster (Sub-millisecond session & query cache).
5. Connect Aurora Primary to Aurora Replica with a dashed edge labeled Synchronous Multi-AZ storage replication.

Review the generated architecture

• Verify that network boundaries clearly separate public subnets from private subnets.
• Check that all AWS components use official vector AWS service icons.
• Verify that replication and target group flows are clearly distinguishable.

Customize the diagram

1. Select the Rectangle tool and create availability zone markers (us-east-1a and us-east-1b) spanning the compute and data tiers.
2. Add security badges (e.g. AWS WAF attached to CloudFront or ALB).
3. If using asynchronous background tasks, add an Amazon SQS queue between ECS tasks.

Export your result

1. Click Export and choose PNG (2x) or SVG to embed into your engineering design doc or presentation slides.
2. Click Export Markdown to capture the AWS cloud topology in standard Markdown.

Tips

• Use official AWS service abbreviations (e.g. ALB, ECS, RDS) in component names to keep labels compact.
• Keep bounding containers spacious to reflect high-availability separation between availability zones.

Limitations

• Rekhic provides architectural modeling and visual documentation; it does not deploy infrastructure directly to AWS or generate Terraform HCL.