Putting it all together¶
You now have every building block: shapes, arrows, text, styling, anchors, groups, automatic layout, icons, and variables. This final page assembles them into a real cloud architecture diagram — the kind you might sketch to explain a serverless request flow.
Notice there are no manual coordinates. Layout directives declare the
structure — a labelled AWS Region boundary and one request-flow row — and
SheepText places everything. Icons carry labelside top captions, while
numbered arrows trace the request from a user through the client and into the
region. Keeping this first complete architecture small makes each new layer
visible before you add branches, return routes, and more services in the editor:
Serverless request flow
layout direction right
layout group MainRegion "AWS Region": ApiGateway Lambda
layout row RequestFlow: Users ChatClient MainRegion
use icons aws
Users: icon aws:users labelside top "Users"
ChatClient: icon aws:client labelside top "Chat client"
ApiGateway: icon aws:amazon-api-gateway labelside top "Amazon\nAPI Gateway"
Lambda: icon aws:lambda labelside top "AWS\nLambda"
from Users arrow "(1)" to ChatClient
from ChatClient arrow "(2)" to ApiGateway
from ApiGateway arrow "(3)" to Lambda
The same toolkit scales down as well as up. Here a compact deployment view combines a styled group, an icon, a plain box, and a labelled connector — mixing automatic and manual composition as each part of the picture needs:
Compact deployment view
use icons aws
Users: icon aws:users "Users" size 40 with .nw at (30, 150)
VPC: [
Api: icon aws:server "API host" size 48 with .nw at (260, 60)
Cache: box "cache" fill #fef3c7 with .nw at (450, 75)
] "VPC" fill #0f172a textsize 14 bold
from Users arrow "https" to Api
from Api arrow "read/write" to Cache
That completes the tutorial. Open any example in the editor to experiment, then start sketching your own diagrams.