Architecture diagrams drawn to each vendor's own rules.

# yaml-language-server: $schema=../references/diagram.schema.json
# Starter template: rename the nodes, keep the shape. Render with `orrery render diagram.yaml`.
title: Web app on AWS
subtitle: A container service behind a load balancer, with a database, a cache and file storage
direction: right
# A little extra spacing keeps the line to the bucket clear of the VPC border.
layout: { spacing: 1.15 }

groups:
  aws: { type: aws:cloud }
  region: { type: aws:region, in: aws }
  vpc: { type: aws:vpc, in: region }

nodes:
  users: { icon: aws:users, label: Users }
  alb: { icon: aws:alb, label: Application Load Balancer, in: vpc }
  app: { icon: aws:fargate, label: Web service, note: Amazon ECS on AWS Fargate, badge: x3, in: vpc }
  db: { icon: aws:aurora, label: Orders database, note: Amazon Aurora PostgreSQL, in: vpc }
  cache: { icon: aws:elasticache, label: Session cache, note: Amazon ElastiCache for Valkey, in: vpc }
  files: { icon: aws:s3, label: Uploads, note: Amazon Simple Storage Service, in: region }

edges:
  - users -> alb: HTTPS
  - alb -> app
  # Label all sibling edges or none: a labeled edge takes one extra column.
  - app -> db, cache, files