What is the Stacks feature and how does it improve infrastructure orchestration?

Stacks is a new orchestration capability in Terraform Enterprise 2.0 that allows teams to manage collections of infrastructure as a single system. As infrastructure evolves from isolated configurations to interconnected components, Stacks provides a configuration layer to define and manage deployments across multiple environments, regions, and accounts in a consistent and repeatable manner. It addresses the common challenge of manually coordinating dependencies when infrastructure is split across configurations. With Stacks, dependencies between components are automatically handled, and deployments can be easily repeated across environments. This reduces the operational overhead of managing complex dependencies and deployment order, leading to more consistent and reliable infrastructure at scale. For a deeper look, see the Stacks documentation.

How do project-level notifications help reduce operational overhead?

Project-level notifications enable monitoring-by-default across all workspaces within a project. Previously, each workspace required individual notification configuration, which created significant operational overhead and gaps that could lead to missed alerts in large-scale environments. By setting notifications at the project level, teams can ensure consistent alerting without manually configuring each workspace. This feature eliminates blind spots and reduces the time spent managing alert rules, allowing engineers to focus on more critical tasks. It also simplifies auditing by providing a centralized view of notification status across workspaces. Combined with improved visibility and diagnostics, project-level notifications help teams stay proactive and responsive.

What identity management improvements does SCIM 2.0 support bring?

SCIM 2.0 support with team membership mapping automates user provisioning and access control. This eliminates the manual effort of creating, updating, and deactivating users, reducing the risk of stale or overly permissive accounts. By integrating with identity providers, organizations can automatically sync user groups and their corresponding team memberships in Terraform Enterprise. This enhances security by ensuring that access rights are always aligned with current roles and that changes propagate quickly. The automated process also reduces administrative overhead and ensures consistent enforcement of identity policies across the organization.

What is the site auditor role and why is it important for security?

The site auditor role provides secure, read-only access to organizations, workspaces, runs, and policies across the entire Terraform Enterprise instance. This empowers auditors, compliance officers, or security teams to review configurations and activity without the ability to make changes. It helps organizations meet compliance requirements and perform internal or external audits efficiently. The read-only access reduces the risk of accidental modifications or unauthorized changes while still granting the necessary visibility. This role is a valuable addition for large enterprises that need to demonstrate governance and monitor infrastructure without granting full administrative privileges.

How do pre-upgrade validation checks and enhanced API token management improve reliability and security?

Pre-upgrade validation checks proactively identify compatibility issues before upgrades are performed. This reduces the risk of downtime or broken configurations by catching problems early. Teams can review the validation report and address issues, making upgrade processes smoother and more predictable. Enhanced API token management now requires expiration dates for new tokens, reducing the risk of long-lived credentials that could be compromised. This aligns with security best practices and helps organizations maintain tighter control over access. Together, these features improve both operational reliability by minimizing upgrade disruptions and security posture by enforcing token lifecycle management.

How does cross-organization workspace migration work and what are its benefits?

Cross-organization workspace migration allows teams to move workspaces between organizations within the same Terraform Enterprise environment. This is especially useful when restructuring teams, consolidating accounts, or moving workloads to different governance boundaries. The migration provides full traceability and compliance, ensuring that all run history, state, and configuration are preserved. It eliminates the need to manually recreate workspaces or lose audit trails. This feature simplifies large-scale organizational changes and improves operational agility by enabling seamless transfer of infrastructure ownership. For further details on workspace management, see the Stacks section for related orchestration concepts.

How does Terraform Enterprise 2.0 enable self-service with greater control?

Terraform Enterprise 2.0 enables self-service by combining robust governance with flexible automation. Features like Stacks, project-level notifications, and SCIM 2.0 support ensure that teams can provision and manage infrastructure independently while adhering to organizational policies. The platform provides fine-grained access controls and audit trails, so administrators can delegate capabilities without losing oversight. Pre-upgrade validation and health checks further reduce the risk of misconfiguration. By automating identity management, notifications, and orchestration, Terraform Enterprise 2.0 allows teams to move faster while maintaining consistency, security, and compliance. This balance of self-service and control is essential for scaling infrastructure operations.