Introduction
HashiCorp introduced the Validated Designs program to give enterprise customers and partners a set of recommendations to deliver a resilient, secure, and high-performance deployment of HashiCorp solutions. The purpose of this document is to provide the Platform Team with HashiCorp's validated design for deploying Terraform Enterprise, enabling your organization to embrace and accelerate infrastructure automation practices. By following this approach, you will eliminate ambiguity in deployment options and be able to make project-level decisions with confidence.
Audience
This document is intended for platform engineers, infrastructure architects, DevOps administrators, and cloud operators who want to design, deploy and administer a highly scalable, resilient infrastructure-as-code platform with Terraform Enterprise.
Supported versions
This guide has been validated with the following versions of Terraform Enterprise:
- Terraform Enterprise v202309-1 and above
Language and definitions
HashiCorp is an enabler of multi-cloud strategies, and as such we take this into account when writing designs. While every attempt has been made to use technology-agnostic terminology, we primarily aim to support the three largest cloud service providers (CSPs) together with an on-premise/datacenter architecture. There are some terms which do not translate perfectly between the public cloud and the datacenter. For the sake of clarity, our definitions for these terms are included below.
| Term | Definition |
|---|---|
| Availability zone | A separate failure domain within a logical datacenter. |
| Region | A separate logical datacenter. |
| Public subnet | A network accessible from the public Internet, containing publicly-addressable infrastructure. |
| Private subnet | A network not accessible from the public Internet and whose infrastructural objects are either blocked from connecting to the public Internet or do through a NAT gateway. |