Introduction

The rationale is to provide you with autonomy and control over the code, enabling you to determine the setup of your infrastructure.

Some of the drawbacks of public modules are that they are not always maintained, and they may not be designed to fit your organization’s needs. They do not have the same structure and typically include more complexity which makes them harder to utilize.

Also, since Terraform lacks a normal package manager, this approach allows you to design the modules in your own version control system, adhering to software development best practices.

Absolutely. You are welcome to utilize this for both personal and commercial projects. There is no need for attribution. The license is here. If you do utilize it in a project, please consider sponsoring the project.

Terraform is the most widely used infrastructure as code tool. It is also the most flexible and has the most community support.

However, with Hashicorp’s recent changes to the open source licensing model, it is important to be aware of the implications of using Terraform in your organization. OpenTofu is a project that aims to provide an open source alternative to Terraform and may be more suitable for you to use.

The design of the modules mirrors the structure of an application, enhancing their comprehensibility and integration. They are crafted to be easily grasped by a typical developer, not exclusively for a DevOps or Cloud engineer.

A website is just that - a website, not a ‘website with 6 lambdas and a VPC’. Similarly, an API is just an API, not an ‘API with a EC2 and a security group’. This is the way the modules are designed. They are designed to be simple and easy to understand.