Goal: cloud architecture
Reader: Cloud architects placing workloads on AWS, Kubernetes or IoT platforms. Meta cluster: C — infrastructure & governance Scenarios: 5 · Examples: 5
Scenarios
| Scenario | Tier | Engines | Example files |
|---|---|---|---|
| aws serverless | T2 | plantuml | aws-serverless-architecture.md |
| iot platform | T2 | plantuml | iot-platform.md |
| kubernetes platform | T2 | plantuml | kubernetes-platform.md |
| migration options | T2 | infographic | cloud-migration-approaches.md |
| observability stack | T2 | plantuml | operations-observability-aws.md |
Reading order
PlantUML with the cloud stencil family for anything that must read as a real platform; one family per diagram.
Engines in this goal
infographic— template-driven boards, sequences and comparisonsplantuml— diagrams with icon families and UML/ArchiMate/BPMN semantics
Details, limits and anti-patterns: ../engines/infographic.md · ../engines/plantuml.md.
Palette
Every figure takes its colours from a theme. Pick one in
../styles/palette.md — the token contract, the theme index and the
per-engine blocks all start there.
Most figures in this set want Default. Depart from it for the medium, not the topic: Print when it may be photocopied, Contrast for low vision or large-print handouts, Vivid when it will be projected, Accessible when colour must not be the only cue, Editorial for long-form reading, Slate for technical reference, Pastel when the figure sits inside gentle prose, Nord for a cool Nordic register. Every theme is designed for a light ground — the set has no dark page.
Don't
- Mixing AWS and Azure icon families in one view
- An architecture diagram with no network boundary or account scope