2014-07-16 23:51:48 +02:00
|
|
|
---
|
|
|
|
layout: "intro"
|
|
|
|
page_title: "Terraform vs. Chef, Puppet, etc."
|
|
|
|
sidebar_current: "vs-other-chef"
|
2014-10-22 05:21:56 +02:00
|
|
|
description: |-
|
2021-07-01 17:01:21 +02:00
|
|
|
How Terraform compares to configuration management tools like Chef and Puppet.
|
2014-07-16 23:51:48 +02:00
|
|
|
---
|
|
|
|
|
|
|
|
# Terraform vs. Chef, Puppet, etc.
|
|
|
|
|
2014-09-02 20:29:22 +02:00
|
|
|
Configuration management tools install and manage software on a machine
|
|
|
|
that already exists. Terraform is not a configuration management tool,
|
|
|
|
and it allows existing tooling to focus on their strengths: bootstrapping
|
|
|
|
and initializing resources.
|
2014-07-16 23:51:48 +02:00
|
|
|
|
2020-10-24 03:05:19 +02:00
|
|
|
Terraform focuses on the higher-level abstraction of the datacenter and
|
|
|
|
associated services, while allowing you to use configuration management
|
|
|
|
tools on individual systems. It also aims to bring the same benefits of
|
|
|
|
codification of your system configuration to infrastructure management.
|
|
|
|
|
|
|
|
If you are using traditional configuration management within your compute
|
|
|
|
instances, you can use Terraform to configure bootstrapping software like
|
|
|
|
cloud-init to activate your configuration management software on first
|
|
|
|
system boot.
|