What is the difference between Terraform Stacks and traditional workspace management?

Terraform Stacks adds a management layer above individual workspaces, allowing you to treat multiple state files as a single deployment unit. While traditional workspaces require separate plan/apply operations for each state file and manual dependency coordination, Stacks automates provisioning across workspaces, manages dependencies through deferred changes, and applies orchestration rules to control deployment workflows across all related workspaces simultaneously.

Can I use Terraform Stacks with the open-source Terraform CLI?

No, Terraform Stacks is currently exclusive to HCP Terraform and cannot be used with the community edition. HashiCorp has indicated in blog posts that some Stacks functionality may be integrated into the community version in the future, but no timeline has been provided. The feature is currently in public beta with a 500-resource limit across all HCP Terraform pricing tiers.

How do Deferred Changes handle dependencies between components?

When a component's provider configuration references outputs from another component (such as a Kubernetes provider needing an EKS cluster endpoint), Stacks automatically recognizes the dependency and defers the plan rather than failing. Once the dependency component is applied and outputs are available, Stacks automatically re-runs the deferred plan. This eliminates the need to manually sequence deployments or work around missing state data during initial provisioning.

Managing Infrastructure at Scale with Terraform Stacks

Name: Managing Infrastructure at Scale with Terraform Stacks
Uploaded: 2026-04-09T17:36:13-04:00
Duration: 24 min
Description: TL;DR Terraform Stacks is a new HCP Terraform feature (public beta) that manages multiple workspaces as a single deployment unit, solving operational complexity when state files are divided across environments and resource types The architecture uses f...

HashiCorp

04/09/2026

0 (0%)

Report Like Favorite

TL;DR

Terraform Stacks is a new HCP Terraform feature (public beta) that manages multiple workspaces as a single deployment unit, solving operational complexity when state files are divided across environments and resource types
The architecture uses four core components: Components for resource definitions, Deployments for environment targeting, Orchestration Rules for automated workflows, and Deferred Changes for automatic dependency management
Orchestration rules enable environment-specific automation, such as auto-approving development deployments while requiring manual approval for production, reducing repetitive approval overhead
Deferred Changes automatically delays component plans when provider configuration depends on outputs from other components, enabling multi-step deployments like EKS clusters followed by Kubernetes manifests without manual coordination
Currently limited to HCP Terraform with a 500-resource cap across all pricing tiers; HashiCorp plans to integrate some functionality into the community edition in the future

The State File Division Problem

The session opens by addressing a fundamental challenge in Terraform infrastructure management: how to properly divide state files as infrastructure scales. When all environments exist in a single monolithic state file, teams face significant risks including unintended changes to production when modifying development resources, extended execution times as API calls multiply, and unclear ownership boundaries when multiple teams manage different resource types. The speaker illustrates how dividing state files by environment (Prod, Stage, Dev) and resource type (network, compute, database) can transform one state file into twelve separate workspaces, improving isolation and team autonomy but introducing new operational complexity.

Terraform Stacks Architecture and Components

Terraform Stacks introduces a new abstraction layer above workspaces to manage multiple state files as a unified deployment unit. The architecture consists of four core elements: Components define infrastructure resources using standard Terraform code wrapped in new component blocks; Deployments specify target environments including AWS accounts, regions, and IAM roles; Orchestration Rules automate approval workflows and plan execution based on environment-specific policies; and Deferred Changes automatically manage dependencies between components by delaying plans when provider configuration depends on outputs from other components. This structure enables teams to deploy multi-account, multi-region infrastructure configurations while maintaining clear dependency relationships and reducing manual coordination overhead.

Practical Implementation and Current Limitations

The demonstration walks through deploying API Gateway, Lambda, and S3 resources across multiple AWS accounts and regions using Terraform Stacks. The speaker shows how orchestration rules can automate deployments to development and staging environments while requiring manual approval for production, and how deferred changes handle complex scenarios like deploying Kubernetes manifests that depend on EKS cluster endpoints. Currently in public beta and exclusive to HCP Terraform (not available in the community edition), Stacks has a 500-resource limit across all pricing tiers. HashiCorp has indicated some functionality may eventually be integrated into the community version, though timing remains unspecified.

Chapters

0:00 - Introduction and Speaker Background
1:13 - State File Division Challenges
5:26 - Introducing Terraform Stacks
8:01 - Stacks Configuration Elements
8:57 - Components Deep Dive
11:09 - Deployments Configuration
13:42 - Creating Stacks in HCP Terraform
16:02 - Orchestration Rules
18:23 - Deferred Changes Feature
22:17 - Conclusion and Resources

Key Quotes

1:20 "First, I think there is a problem with state files that are not properly divided."
5:26 "I think that Terraform Stacks can be used to solve such problems."
6:17 "This function is a function that allows you to simplify large-scale infrastructure management."
6:38 "As a precaution, it can only be used in Terraform."
7:05 "Since this is a public beta, there is a limit to the number of resources. There is a limit of up to 500 resources."
10:53 "Since this is received by the output, the dependency relationship is automatically taken into account, and this is taken into account when planning or applying."

Categories:

Tags:

Show more Show less

Browse videos

Upcoming Webinar Calendar

05/12/2026

11:30 PM

05/12/2026

Implementing Effective Strategies for Active Directory Security and Data Protection

https://www.truthinit.com/index.php/channel/1888/implementing-effective-strategies-for-active-directory-security-and-data-protection/
05/13/2026

01:00 AM

05/13/2026

Transforming the Black Box: Reveal Hidden Threats and AI Risks through Data Lineage

https://www.truthinit.com/index.php/channel/1890/transforming-the-black-box-reveal-hidden-threats-and-ai-risks-through-data-lineage/
05/13/2026

05:00 AM

05/13/2026

Transforming the Black Box: Revealing AI Risks and Hidden Threats through Data Lineage

https://www.truthinit.com/index.php/channel/1894/transforming-the-black-box-revealing-ai-risks-and-hidden-threats-through-data-lineage/
05/19/2026

01:00 PM

05/19/2026

Establishing a Robust AI Governance Framework for GenAI Throughout Deployment Phases

https://www.truthinit.com/index.php/channel/1936/establishing-a-robust-ai-governance-framework-for-genai-throughout-deployment-phases/
05/20/2026

08:00 AM

05/20/2026

Establishing a Robust AI Governance Framework for GenAI Throughout Its Lifecycle

https://www.truthinit.com/index.php/channel/1937/establishing-a-robust-ai-governance-framework-for-genai-throughout-its-lifecycle/
05/20/2026

10:00 PM

05/20/2026

Establishing a Robust AI Governance Framework for GenAI Throughout Its Lifecycle

https://www.truthinit.com/index.php/channel/1953/establishing-a-robust-ai-governance-framework-for-genai-throughout-its-lifecycle/
05/21/2026

11:00 AM

05/21/2026

The Autonomous Era: Orchestrating a Resilient Enterprise

https://www.truthinit.com/index.php/channel/1372/the-autonomous-era-orchestrating-a-resilient-enterprise/
05/27/2026

04:00 AM

05/27/2026

Rivoluziona i rischi dell'AI in opportunità con Netskope AI Security

https://www.truthinit.com/index.php/channel/1925/rivoluziona-i-rischi-dellai-in-opportunità-con-netskope-ai-security/
05/27/2026

10:00 AM

05/27/2026

Harnessing AI: Transitioning from Illusion to Purposeful Mastery

https://www.truthinit.com/index.php/channel/1924/harnessing-ai-transitioning-from-illusion-to-purposeful-mastery/
05/28/2026

01:00 PM

05/28/2026

Harnessing AI for Smaller Teams: Strategies for Secure Implementation

https://www.truthinit.com/index.php/channel/1951/harnessing-ai-for-smaller-teams-strategies-for-secure-implementation/
06/02/2026

01:00 PM

06/02/2026

Spring of Satori: Delving into Recent Findings and the 2026 Threat Landscape

https://www.truthinit.com/index.php/channel/1930/spring-of-satori-delving-into-recent-findings-and-the-2026-threat-landscape/
06/04/2026

02:00 AM

06/04/2026

Mastering the Unseen: Managing Shadow AI and Agentic MCP Traffic

https://www.truthinit.com/index.php/channel/1948/mastering-the-unseen-managing-shadow-ai-and-agentic-mcp-traffic/
06/16/2026

07:00 AM

06/16/2026

Transforming Data Risk into Actionable Priorities: Essential Fixes First

https://www.truthinit.com/index.php/channel/1952/transforming-data-risk-into-actionable-priorities-essential-fixes-first/