Methodology: the workflow described in the referenced AWS Builder article (Amazon Q CLI paired with the AWS Diagram MCP Server) generates a diagram by having an LLM author Python code against the
diagrams library, which Graphviz then renders using that library's bundled AWS icon set. In this environment, Graphviz could not be installed without root access, so an equivalent approach was used instead: the same official icon assets bundled by the diagrams library were sourced from its public GitHub repository and positioned manually within the SVG below. The icon source is identical; only the layout step differs — manual placement in place of Graphviz's automatic layout.
Request / data flow
Secrets & observability (cross-cutting)
AWS Cloud boundary
VPC — private subnets
Icons: official AWS Architecture Icons, sourced via the mingrammer/diagrams library's bundled asset set (the same icons the AWS Diagram MCP Server / Python diagrams DSL draws from). Reference workflow: How to Generate AWS Architecture Diagrams Using Amazon Q CLI and MCP — note a commenter on that article flags the specific MCP server as decommissioned since publication, which is what pushed this doc to the manual-placement approach above instead.