Modules are defined with module blocks. They are used for the reusability of the code, suppose you have a stack that can be re-used. In such a case instead of copy-paste the same resource code, again and again, we define a module.
Any folder containing a configuration file is by default considered as a module in Terraform.
These modules are referenced in the module code block.
Modules do contain input and outputs.
The module looks similar to resources, they just don’t have types. Each module must have unique names, in the configuration. Modules only have one required parameter, i.e. source.
Modules can be stored in local as well as remote locations,
- Github
- Local
- Terraform Registry
- Gitbucket
- HTTP URL
- S3 Bucket
- GCS Bucket
Note – You may need to run the terraform init command to call the module file. In case of any update in the module file, you will need to run terraform init command in order to get those module updates reflected in your terraform configuration, failure to do so will result in the below error.
$ terraform init
