![\"\"](\"https:\/\/uplatz.com\/blog\/wp-content\/uploads\/2025\/06\/Blog-images-new-set-A-16.png\")
<\/p>\n
- \n
- Overview and Core Concepts<\/b><\/li>\n<\/ol>\n
Terraform<\/b><\/p>\n
Terraform is an open-source IaC tool by HashiCorp that uses the HashiCorp Configuration Language (HCL) to define infrastructure resources. It supports over 130 official and 160 community-maintained providers, enabling multi-cloud and hybrid deployments through a consistent workflow across AWS, Azure, GCP, and on-premises platforms<\/span>.<\/span><\/p>\n
AWS CloudFormation<\/b><\/p>\n
CloudFormation is a fully managed AWS service that uses JSON or YAML templates to model and provision AWS and supported third-party resources as a stack. It automates resource creation, updates, and deletion, handling dependencies and drift detection natively within the AWS ecosystem<\/span>.<\/span><\/p>\n
- \n
- Language and Template Syntax<\/b><\/li>\n<\/ol>\n
- \n
- Terraform uses HCL, a purpose-built declarative language designed for readability, modularity, and expression of complex logic through features like <\/span>count<\/span>, <\/span>for_each<\/span>, and <\/span>dynamic<\/span> blocks<\/span>.<\/span><\/li>\n
- CloudFormation relies on JSON or YAML. Templates consist of sections such as <\/span>Resources<\/span>, <\/span>Parameters<\/span>, <\/span>Mappings<\/span>, <\/span>Conditions<\/span>, and <\/span>Outputs<\/span>. YAML is often preferred for readability and comments, while JSON may benefit existing JSON-centric workflows<\/span>.<\/span><\/li>\n<\/ul>\n
- \n
- State Management<\/b><\/li>\n<\/ol>\n
Terraform State<\/b><\/p>\n
Terraform maintains a <\/span>.tfstate<\/span> file that tracks resource metadata and dependencies. By default, this state is local but can be stored remotely (e.g., AWS S3, Azure Blob, GCP Storage) to enable team collaboration, locking, and remote data sharing via the <\/span>terraform_remote_state<\/span> data source<\/span>.<\/span><\/p>\n
CloudFormation State<\/b><\/p>\n
CloudFormation manages state internally within AWS. Users do not directly access state files; AWS tracks stack metadata automatically. Drift detection can be performed via the console or API to compare actual resource configurations against the template definitions<\/span>.<\/span><\/p>\n
- \n
- Execution Model and Workflow<\/b><\/li>\n<\/ol>\n
\n\n
\n Workflow Stage<\/span><\/td>\n Terraform<\/span><\/td>\n CloudFormation<\/span><\/td>\n<\/tr>\n \n Planning<\/span><\/td>\n terraform plan<\/span> generates an execution plan showing planned changes and diffs<\/span><\/td>\n Change Sets preview proposed updates before execution<\/span><\/td>\n<\/tr>\n \n Execution<\/span><\/td>\n terraform apply<\/span> applies the plan in parallel based on the resource graph<\/span><\/td>\n CreateStack<\/span> \/ <\/span>UpdateStack<\/span> actions execute sequentially with dependency resolution by AWS<\/span><\/td>\n<\/tr>\n \n Rollback on Failure<\/span><\/td>\n No automatic rollback; requires manual or scripted corrective actions<\/span><\/td>\n Automatic rollback on stack creation\/update failure by default<\/span><\/td>\n<\/tr>\n \n Modularization<\/span><\/td>\n Reusable modules packaged locally or via Terraform Registry<\/span><\/td>\n Nested stacks enable template reuse, but modularity is less flexible<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/p>\n
- \n
- Multi-Cloud and Extensibility<\/b><\/li>\n<\/ol>\n
- \n
- Terraform<\/b> shines in multi-cloud scenarios, supporting numerous providers via plugins and allowing a single codebase to target AWS, Azure, GCP, Kubernetes, and more<\/span>.<\/span><\/li>\n
- CloudFormation<\/b> is AWS-centric. Third-party and partner-published resource types are available through the CloudFormation Registry, but true multi-cloud orchestration requires external tooling or CDK constructs<\/span>.<\/span><\/li>\n<\/ul>\n
- \n
- Ecosystem and Community Support<\/b><\/li>\n<\/ol>\n
- \n
- Terraform benefits from a large open-source community, extensive provider ecosystem, community modules, and enterprise features (Sentinel policy as code, private module registry)<\/span>.<\/span><\/li>\n
- CloudFormation offers deep integration with AWS services, built-in drift detection, guardrails via StackSets, and AWS CDK support for writing constructs in familiar programming languages (TypeScript, Python, Java, \u2026)<\/span>.<\/span><\/li>\n<\/ul>\n
- \n
- Error Handling and Drift Detection<\/b><\/li>\n<\/ol>\n
- \n
- Terraform provides detailed error messages and plan diffs, but drift detection is manual via comparing remote state with actual resource configurations. External tools like <\/span>terraform plan<\/span> can expose drift changes<\/span>.<\/span><\/li>\n
- CloudFormation includes automatic dependency analysis, resource drift detection, and comprehensive drift reports in the console and API for stacks and individual resources<\/span>.<\/span><\/li>\n<\/ul>\n
- \n
- Pricing and Governance<\/b><\/li>\n<\/ol>\n
- \n
- Terraform Open Source<\/b> is free; Terraform Cloud\/Enterprise offers commercial features such as remote runs, policy enforcement, collaboration, and private registries at added cost.<\/span><\/li>\n
- CloudFormation<\/b> is free; you pay only for the AWS resources it provisions. Governance can be enforced via AWS Organizations SCPs, IAM policies, and StackSets permissions.<\/span><\/li>\n<\/ul>\n
- \n
- Decision Criteria<\/b><\/li>\n<\/ol>\n
Choose Terraform When:<\/b><\/p>\n
- CloudFormation<\/b> is free; you pay only for the AWS resources it provisions. Governance can be enforced via AWS Organizations SCPs, IAM policies, and StackSets permissions.<\/span><\/li>\n<\/ul>\n
- Terraform Open Source<\/b> is free; Terraform Cloud\/Enterprise offers commercial features such as remote runs, policy enforcement, collaboration, and private registries at added cost.<\/span><\/li>\n
- CloudFormation includes automatic dependency analysis, resource drift detection, and comprehensive drift reports in the console and API for stacks and individual resources<\/span>.<\/span><\/li>\n<\/ul>\n
- Terraform provides detailed error messages and plan diffs, but drift detection is manual via comparing remote state with actual resource configurations. External tools like <\/span>terraform plan<\/span> can expose drift changes<\/span>.<\/span><\/li>\n
- CloudFormation offers deep integration with AWS services, built-in drift detection, guardrails via StackSets, and AWS CDK support for writing constructs in familiar programming languages (TypeScript, Python, Java, \u2026)<\/span>.<\/span><\/li>\n<\/ul>\n
- Terraform benefits from a large open-source community, extensive provider ecosystem, community modules, and enterprise features (Sentinel policy as code, private module registry)<\/span>.<\/span><\/li>\n
- CloudFormation<\/b> is AWS-centric. Third-party and partner-published resource types are available through the CloudFormation Registry, but true multi-cloud orchestration requires external tooling or CDK constructs<\/span>.<\/span><\/li>\n<\/ul>\n
- Terraform<\/b> shines in multi-cloud scenarios, supporting numerous providers via plugins and allowing a single codebase to target AWS, Azure, GCP, Kubernetes, and more<\/span>.<\/span><\/li>\n
- Multi-Cloud and Extensibility<\/b><\/li>\n<\/ol>\n
- Execution Model and Workflow<\/b><\/li>\n<\/ol>\n
- CloudFormation relies on JSON or YAML. Templates consist of sections such as <\/span>Resources<\/span>, <\/span>Parameters<\/span>, <\/span>Mappings<\/span>, <\/span>Conditions<\/span>, and <\/span>Outputs<\/span>. YAML is often preferred for readability and comments, while JSON may benefit existing JSON-centric workflows<\/span>.<\/span><\/li>\n<\/ul>\n
- Terraform uses HCL, a purpose-built declarative language designed for readability, modularity, and expression of complex logic through features like <\/span>count<\/span>, <\/span>for_each<\/span>, and <\/span>dynamic<\/span> blocks<\/span>.<\/span><\/li>\n
- Language and Template Syntax<\/b><\/li>\n<\/ol>\n