Terraform provisions infrastructure with a declarative configuration language.
count
and for_each
allow you to provision multiple instances of infrastructure (either resources or entire modules) using a single block of configuration code.
Use both of these features through new hands-on tutorials on HashiCorp Learn.
count
to flexibly scale EC2 instances in a VPC.for_each
to provision entire duplicate VPCs for multiple projects.When using count
, Terraform will replicate the given resource a specified number of times. The following example will provision two similar instances using the same block of configuration.
You can also use a variable to define the number of resources provisioned with count
, making the configuration even more flexible.
Like count
, for_each
will provision multiple resources, but instead of using an integer to define the number of resources, for_each
uses a data structure, creating one copy of the given resource for each item in the data structure. This allows you to configure the individual resources in more complex ways. The following configuration will provision a VPC for each element in the map called project
, each with a configurable number of public and private subnets.
Together, these two features allow you to configure duplicate resources of the same type while maintaining the simplicity of Terraform’s declarative configuration language.
With the recent release of Terraform 0.13, Terraform supports both of these features with modules as well as resources. Try these and other 0.13 tutorials on HashiCorp Learn.
ServiceNow Service Catalog for Terraform now lets users provision infrastructure powered by no-code modules published in their organization’s private registry.
No-code provisioning module version upgrades are now GA in HCP Terraform, providing validated self-service infrastructure to reduce toil and lower cloud spend.
Do cloud right with The Infrastructure Cloud from HashiCorp. Unlock developer potential while controlling cloud costs and risk.