As a Learner, I kept getting asked "what does our AWS setup actually look like?" and had no good answer. The AWS console shows you one service at a time. You never see the full picture: which Lambda triggers which SQS, which SQS feeds which RDS, where the actual data flows. I built CloudWire because I wanted to see my infrastructure the way it actually runs, not the way AWS organizes its nav menu. Started as a simple script that dumped Lambda and SQS connections into a JSON file. Then I added a browser UI. Then more services. Then tag-based scanning. Then Terraform import. Then VPC topology with internet exposure detection. The core insight that kept expanding the scope: every AWS resource is just a node, and every integration is just an edge. Once you commit to that mental model, adding a new service is just writing one more scanner mixin. The architecture found its own shape by following that idea to its conclusion.

cloudwire

Map your AWS infra as a live graph. Runs locally.

Map your AWS infra as a live graph. Runs locally.