HCP Terraform + Infragraph: A Live Map of Your Entire Cloud Estate

Most organizations use five or more tools to understand their cloud estate — and by the time the data is consolidated, it’s already stale. HashiCorp’s Infragraph, now in public preview, builds that map automatically from live infrastructure sources.

Context

Multi-cloud estates create data silos by design. AWS Config, Azure Resource Graph, GCP’s Asset Inventory, and Terraform state files each answer different questions about different scopes. Reconciling them into a single picture of what is running, who owns it, and whether it matches declared state requires manual effort that most platform teams can’t sustain on a continuous basis.

The result is “dirty data”: infrastructure reports accurate as of the last export and unreliable as of right now. Teams discover drift, unmanaged resources, and orphaned dependencies through incidents rather than proactive monitoring.

HashiCorp has been building toward this capability methodically. Stack Archive has previously covered Terraform’s drift detection capabilities and HashiCorp’s Vault-based identity framework for AI agent access. Infragraph is the visibility layer of that same platform — the persistent knowledge graph that makes proactive management possible rather than reactive.

The Detail

Infragraph is an event-driven knowledge graph embedded in HCP Terraform. Instead of scheduled reconciliation jobs, it maintains direct connections to AWS, Azure, GCP, and on-premises systems that push updates automatically as infrastructure changes. The result is a continuously current map of every resource across the estate, with metadata covering ownership, configuration state, Terraform version, and management status.

Teams can query that graph through a natural language interface — asking which resources are unmanaged by Terraform, which providers are running outdated versions, or which workspaces have unresolved drift. That query layer matters for platform teams that don’t write Terraform query syntax fluently, or for surfacing operational intelligence without a dedicated reporting workflow.

The technical architecture integrates HCP Terraform, HCP Packer, and custom data streams via Terraform Search, supplementing cloud provider APIs with the infrastructure-as-code layer Terraform manages. Announced at IBM Think 2026, the public preview opens May 8 for qualified US HCP Terraform customers. The graph is explicitly designed to serve as the context layer for AI-driven remediation workflows — an agent that needs to act on drift or misconfiguration needs to know what is deployed and who owns it.

The Pattern

Stack Archive has covered five HashiCorp platform posts over the past 90 days: Vault secrets management, Vault SPIFFE identity for AI agents, SSH access controls, HCP multi-owner governance, and Terraform drift detection. Infragraph is the visibility layer that makes each of those governance capabilities operationally useful — you cannot remediate drift or enforce policy on resources you cannot see in real time.

Source: HashiCorp

Content created with AI assistance and reviewed for accuracy.