Nadie mantiene al día el diagrama de red de AWS. He hecho una herramienta para eso
VPC Atlas lee una cuenta de AWS con llamadas de solo lectura y dibuja su red en draw.io y Lucidchart. Alfa, licencia MIT. En todos los equipos a los que me he incorporado, lo primero que pedían era lo mismo: el diagrama de red. El que muestra cada VPC, cómo se conectan las VPC entre sí a través de Transit Gateways, peerings, VPN y Direct Connect, y qué hay en el borde, delante de ellas. Y todas…
AWS VPC Atlas is a tool that creates network diagrams of AWS accounts. It reads a AWS account and draws the network in draw.io and Lucidchart. The tool is licensed under MIT and is used by various teams to maintain accurate network diagrams, which are often outdated. The diagrams show each VPC, how they connect to each other through Transit Gateways, peerings, VPNs, and Direct Connect, and what is on the edge in front of them.
VPC Atlas reads the AWS API Describe*, Get*, List*, and Search* endpoints, but never creates, changes, or deletes anything. It gets the minimum policy it needs, so you can read what it asks for before granting it. The tool produces three types of output: diagrams, an inventory, and a dashboard. The diagrams are in .drawio and .lucid formats, using AWS Architecture Icons and following AWS's multicloud landing zone reference.
The inventory is in JSON, Markdown, and HTML, with each resource accounted for by account and sections for each external account it is linked to. The dashboard shows the diagrams in the browser, keeps a history of scans, and draws the difference between two scans. The raw output is also saved as vpcatlas-graph.json for redrawing without calling AWS again.
The tool has four stages: collection, graph, layout, and exportation. Each stage has an input and output. The collection stage uses service collectors that are paginated. Regions are processed in parallel, and individual collectors are processed one after another within a region to keep API throttling low. Failed AccessDenied calls are logged and skipped.
The graph stage converts the results into a directed graph using networkx and Pydantic models. The layout stage calculates positions for the diagram using a deterministic grid: cloud, region, VPC, availability zone, and subnet. The export stage produces three outputs: XML for mxGraph for draw.io, a Lucid Standard Import package for Lucid, and the inventory in JSON, Markdown, and HTML.
The tool uses a consistent numbering system for arrows, which distinguishes traffic types across pages.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
