// the find
cycloidio/inframap
Read your tfstate or HCL to generate a graph specific for each provider, showing only the resources that are most important/relevant.
InfraMap takes a Terraform state file or HCL and produces a readable graph of your infrastructure by filtering out noise — intermediate resources like security group rules become edges rather than nodes, so you see EC2 talking to RDS, not a soup of rule resources in between. It outputs DOT format, so you pipe it to Graphviz or graph-easy. For platform engineers tired of staring at `terraform graph` output that looks like a circuit diagram exploded.
AWS support is genuinely useful — the edge-collapsing logic for security groups, NAT gateways, and load balancers meaningfully reduces visual clutter compared to raw `terraform graph`. The `prune` subcommand that strips sensitive values before sharing state files is a practical addition that most similar tools skip. The `--raw` escape hatch lets you see exactly what the tool read before any provider-specific logic runs, which makes debugging empty graphs tractable. Docker image ships with Graphviz pre-installed, so the one-liner from stdin to PNG actually works without a separate install step.
IAM connections are unimplemented for every provider — the table in the README marks it as missing everywhere — which means for AWS in particular you're missing the most important class of relationships in any non-trivial setup. VPC/region grouping is still WIP after years on the tracker. Azure and GCP support is essentially 'dump everything without any simplification', which is barely more useful than the raw Terraform graph. Last meaningful activity suggests this is in maintenance mode; the core provider logic is static Go files that need manual updates every time Terraform adds or renames resources, and there's no mechanism to keep that current.