inframap
Reads Terraform state or HCL files to generate simplified, provider-specific infrastructure graphs.
What is inframap?
InfraMap is a CLI tool that generates simplified, readable graphs from Terraform state files or HCL configurations. It helps DevOps engineers and cloud architects visualize their infrastructure by focusing on the most relevant resources and connections, making complex setups easier to comprehend. Unlike Terraform's built-in graph command, it applies provider-specific logic to reduce clutter and improve clarity.
DevOps engineers, SREs, and cloud architects who manage infrastructure with Terraform and need to visualize or document their cloud resources.
Developers choose InfraMap because it produces cleaner, more focused graphs than `terraform graph`, with provider-aware simplifications that highlight what matters. It supports multiple cloud providers and offers security features like state file pruning.
Overview
Read your tfstate or HCL to generate a graph specific for each provider, showing only the resources that are most important/relevant.
Use Cases
Best For
- Visualizing AWS, GCP, or Azure Terraform deployments
- Documenting infrastructure dependencies for onboarding
- Simplifying complex Terraform graphs for presentations
- Analyzing HCL configurations without applying them
- Sharing infrastructure layouts with non-technical stakeholders
- Debugging Terraform resource connections
Not Ideal For
- Projects requiring complete, unfiltered dependency graphs for automated analysis or debugging
- Infrastructure heavy on IAM configurations, as IAM connections are not supported
- Teams using niche cloud providers without specific logic (e.g., non-listed providers), where graphs remain cluttered
- Environments relying solely on Terraform backends like S3 or GCS without local state pulls, necessitating workarounds
Pros & Cons
Pros
Applies custom logic for AWS, GCP, Azure, and others to filter out noise, producing significantly cleaner graphs than Terraform's raw output, as shown in the README's comparison images.
Works with both Terraform state files (versions 3-4) and HCL configurations directly, allowing analysis without applying changes, per the usage examples.
Offers flags like `--raw` for unprocessed output and `--connections=false` to hide lines, giving users fine control over visual detail, demonstrated in the example outputs.
Includes a `prune` subcommand to remove sensitive data from state files before sharing, enhancing security for collaboration, though HCL pruning is not yet supported.
Cons
Advanced capabilities like grouping and external nodes are only available for AWS, and IAM connections are unsupported for all providers, limiting utility for complex infrastructures, as acknowledged in the provider table.
The `prune` subcommand does not yet work with HCL configurations, which can be a security gap when sharing raw configs, as noted in the usage section.
Visualization requires separate installations like Graphviz or graph-easy, adding setup complexity and potential compatibility issues, as shown in the installation and usage instructions.
Frequently Asked Questions
Related Projects
terraformerCLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code
InfracostCloud cost intelligence for engineers, AI coding agents, and CI/CD 💰📉 Shift FinOps Left!
TerragruntTerragrunt is a flexible orchestration tool that allows Infrastructure as Code written in OpenTofu/Terraform to scale.
atlantisTerraform Pull Request Automation
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.