AI AWS architecture diagram generator.
From the Terraform you already have, with no read-only role to provision and nothing sent anywhere.
Sources it reads
Terraform, CloudFormation templates, CDK synthesised output, SAM templates, and JSON from describe commands if that is what you have. Each of them fully describes the infrastructure, and each of them is a file on disk, which is why none of this requires access to the account it describes.
How Lucid Train draws one
Describe what you want, or point it at a repository. The agent emits a semantic graph of nodes and edges with no coordinates, and the ELK layout engine computes positions and orthogonal routing. That separation is the reason the output cannot come back with boxes overlapping or arrows crossing through cards, which is the characteristic failure when a language model is asked to place things on a canvas itself. It also means editing is editing the graph: change a component and the layout re-solves rather than drifting out of alignment.
Tiers rather than VPC boxes
The default AWS diagram convention nests everything inside VPC and subnet rectangles, which spends most of the picture on network structure. Grouping by tier instead puts the emphasis on what the system does, with network placement as an annotation. If the network genuinely is the subject, that is a different diagram and worth drawing separately.
Queues as edges, not boxes
SQS, SNS and EventBridge are drawn as the connection between producer and consumer rather than as nodes traffic passes through. That keeps the component count down and matches how people describe these systems out loud, where nobody says a request visits the queue.
Local, offline, your models
It runs as a desktop application. Against a local Ollama model the whole thing works offline with no API key and no telemetry, which is the practical difference from every browser-based diagram tool: your architecture never leaves the machine.
AWS services by tier
| Service | Tier |
|---|---|
| CloudFront, Route 53, WAF | Edge |
| API Gateway, ALB, NLB | Edge |
| EC2, ECS, EKS, Fargate | Application |
| Lambda, Step Functions | Application |
| RDS, Aurora, DynamoDB | Data |
| S3, EFS, FSx | Data |
| ElastiCache, MemoryDB | Data |
| SQS, SNS, EventBridge, Kinesis | Drawn as edges |
| Cognito, IAM, Secrets Manager | Authentication boundary |
| CloudWatch, X-Ray | Infrastructure |
Try it
Questions
Does it need AWS credentials?
No, and it never asks for them. Everything comes from files.
Does it work with CDK?
Yes, from the synthesised template. Reading CDK TypeScript directly works too but is less reliable, since the template is what actually gets deployed.
Can it show multi-region architecture?
Yes, with regions as sections. Cross-region edges are worth marking explicitly since they are where latency and data transfer cost accumulate.
How does this compare with the AWS architecture icons in draw.io?
Those give you a palette and you do the drawing. Here the diagram is generated from your infrastructure code and laid out by a solver, so it starts from what you actually deployed rather than from a blank canvas.
Related
- AI Azure Architecture Diagram GeneratorFrom Bicep, ARM or Terraform, without granting a reader role on the subscription.
- AI GCP Architecture Diagram GeneratorFrom the Terraform in your repository, with no project access and nothing uploaded.
- AI Kubernetes Architecture Diagram GeneratorThe topology is in the YAML. It is just spread across forty files and expressed as label matches.
- AI Microservices Diagram GeneratorThe interesting question is never how many services there are, it is which ones cannot be deployed without the others.
Last updated