Generate an AWS architecture diagram.
It reads your infrastructure as files rather than by connecting to your account, which means it needs no credentials and works against environments you cannot reach.
It reads files, not your account
There is no credential field and that is deliberate. Terraform, CloudFormation, CDK output, or the JSON from a describe command all work, and any of them can be diagrammed from a laptop with no access to the account in question. A tool that asks for production read access to draw a picture is asking for a great deal in return for very little, and it also cannot help you with an environment you are not permitted to reach.
How AWS resources become components
Services map onto tiers in the way people already think about them: CloudFront, API Gateway and load balancers at the edge; EC2, ECS, EKS and Lambda in the application tier; RDS, DynamoDB, S3 and ElastiCache in data; SQS, SNS and EventBridge drawn as the edges they are rather than as boxes traffic passes through. VPC and subnet structure becomes grouping rather than nodes, because a diagram in which the network is boxes is a network diagram, which is a different picture.
Why the layout can be trusted
The agent reads the files listed above and emits a semantic graph: components, the tier each belongs to, and the edges between them, with no coordinates anywhere. The ELK layout engine then computes positions and orthogonal edge routing. This is why the output cannot come back with boxes overlapping or arrows crossing through cards, which is the usual failure when a language model is asked to place things on a canvas itself.
Official icons, offline
Service logos are bundled with the app rather than fetched, so diagrams render identically with no network at all. That matters more than it sounds: a diagram that silently loses its icons in an air-gapped environment or on a plane is a diagram you cannot rely on for a review.
Nothing leaves your machine
It runs on your machine. With a local Ollama model nothing leaves the laptop at all, and with your own API key the file contents go to the provider you chose and never through us. For a source that is your actual codebase, that distinction is usually the deciding one.
AWS services to diagram tiers
| Service | Tier |
|---|---|
| CloudFront, Route 53 | Edge |
| API Gateway, Application Load Balancer | Edge |
| EC2, ECS, EKS, Fargate | Application |
| Lambda | Application, drawn as a function |
| RDS, Aurora, DynamoDB | Data |
| S3, EFS | Data |
| ElastiCache | Data |
| SQS, SNS, EventBridge, Kinesis | Edges between components |
| Cognito, IAM | An authentication boundary |
| VPC, subnets, security groups | Grouping and notes, not nodes |
The prompt
Questions
Related
- Generate a Diagram from a CodebasePoint it at a repository and it surveys the code the way a new engineer would, then draws what it found.
- Generate a Diagram from TerraformTerraform already describes your infrastructure precisely. The diagram is a rendering of something you have written down, not a guess.
- Generate a Diagram from Kubernetes ManifestsKubernetes YAML contains the whole topology and presents it as several hundred lines in which none of it is visible.
- Generate a Diagram from Docker ComposeA Compose file is already a complete description of a small system. It is just written in a format that hides the shape.