Hand-Drawn AWS Architecture Diagram, Cleaned Up
This is what a quick AWS architecture sketch looks like after Sketio has read it: a serverless web app, drawn the way you would on a whiteboard, with a box and a name for each service and an arrow wherever one thing talks to another.
Below are the strokes as they were drawn, and then what Sketio made of them, with nothing changed afterwards.
Generated handwriting. The handwriting on this page was generated by a script that imitates hand-drawn strokes. The cleaned-up diagram is Sketio's actual output, unedited.
What was drawn
Scroll sideways to see the whole picture
- Seven boxes laid out from top to bottom, each with a service name written inside: Users, CloudFront, S3, API Gateway, Lambda, Cognito and DynamoDB.
- Six arrows, each one a single stroke from one service to the next: Users to CloudFront, CloudFront to S3 and to API Gateway, API Gateway to Cognito and to Lambda, and Lambda to DynamoDB.
- The board's reading mode was set to AWS architecture.
What Sketio made of it
Scroll sideways to see the whole picture
Counted from the recording of this board:
- 7 AWS service icons (Users, CloudFront, S3, API Gateway, Lambda, Cognito, DynamoDB)
- 6 connectors: 6 joined to a shape or icon at both ends, 6 with an arrowhead, 0 dashed
- Every name was read correctly from the handwriting.
- Each box with an AWS service name in it became that service's official AWS icon, with the name under it. The boxes themselves were replaced by the icons.
- Every arrow was joined to the two icons it runs between, with the arrowhead at the end where it was drawn to, so the arrows follow the icons if you move them.
What it did not get right
- The icons were laid out where the boxes were, so the diagram is only as tidy as the sketch. Everything sits where it was drawn.
- Nothing in the sketch said what an arrow means (a request, an event, a read). Add a label if the meaning matters.
Opens Sketio's cleaned-up diagram as a board you can edit.
By continuing, you agree to the Terms of Service and Privacy Policy, including sending images of your strokes, diagram labels and similar data to providers in the United States (Cloudflare, Inc. and TypeSafe AI, Inc.) for AI conversion.
When to use it
- Turning a whiteboard sketch from a design discussion into a diagram you can share.
- Drafting a serverless architecture before writing infrastructure code.
- Explaining an AWS design in a ticket or a review without opening an icon library.