Infrastructure as Code provides a convenient way to manage and automate deployments to cloud infrastructure. In this blog, learn how Terraform can be used to perform Infrastructure as Code.
Table of Contents:
If you are planning to automate your cloud infrastructure then nothing could be better than Terraform. Terraform is the most widely used and popular automation (infrastructure as code) tool that allows you to build and manage infrastructure easily and efficiently.
In this Terraform series, you are going to learn from the ground up what Terraform is and what you need to know to manage and build your infrastructure using Terraform.
Prerequisites
This article will be a step by step guide. If you would like to follow along, be sure to have the following in place:
Terraform - This tutorial will use Terraform v1.0.8 running on Ubuntu 18.04.5 LTS, but any operating system with Terraform should work.
Introduction to Terraform
Terraform is a tool for building, versioning, and updating the infrastructure. It is written in GO Language and the syntax language of configuration files is HCL i.e HashiCorp Configuration Language(much easier than YAML or JSON).
Terraform has been in use for quite a while now. It is an amazing tool to build and change the infrastructure in a very effective and simpler way. It can be used with a variety of cloud providers such as Amazon AWS, Oracle, Microsoft Azure, Google Cloud, and many more. Let's learn more about it.
Key Features of Terraform
Terraform as a tool is a big game changer to manage cloud infrastructure because of the ease of writing code which is such that the same code can be easily made to work with various cloud providers. There are several other key features of Terraform which make this tool so popular and handy. Let's discuss a few of them now.
Infrastructure as a code: Terraform execution and configuration files are written in Infrastructure as a code language - a high-level language which is easy to understand.
Execution Plan: Terraform provides you in depth details about the deployment and resources it will create before deploying the actual code.
Resource Graph: Terraform makes the life of an administrator simple by providing a graphical view of the resources that are currently being provisioned or are already provisioned.
Files and Directories in Terraform
Terraform code consists of Terraform configuration files that follow a standard structure - an arrangement of files and directories that improves code readability. Lets checkout details about these files and folders.
Terraform modules are top-level directories. A single module contains mainly five Terraform configuration files: main.tf, vars.tf, providers.tf, output.tf and terraform.tfvars which are written with .tf format or .tf.json or .tfvars format. These are known as root modules.
The Root module can call other child modules from either local directories or Terraform Registry or from anywhere in the disk
As you can see in the below image there are two child modules - AWS EC2 and AWS S3. Modules containing all the required configurations(main.tf, vars.tf, provider.tf, terraform.tfvars etc) are the ROOT modules for themselves but also acts as child module for the other ROOT module that contains both EC2 and AWS S3.
Now, let's dive into five configuration files that a root module requires.
main.tf → The main.tf file contains the main code that defines which resources you need to create or manage the infrastructure. Below is an example of a main.tf file that creates a resource - 'ec2 instance' under which you need to define:
The resource type that you need to create- "aws_instance".
Arguments containing the values- "ami" and "instance_type" of type string.
Timeout is an argument of type map containing "create" and "delete" values.
vars.tf → The vars.tf contains all the variables that the configuration file (main.tf) references. Below is an example of a vars.tf file that contains variables of different types that you refer to in main.tf, such as:
terraform.tfvars → terraform.tfvars contains the values that terraform uses to replace the variables referred inside main.tf.
output.tf → Terraform output configuration provides the output of AWS resources such as arn or IP address after you execute the terraform apply command. Below is an example of output.tf file that provides the resource outputs such as AWS EC2 instance arn, and public IP address after executing the terraform apply command
provider.tf → The provider.tf file is where you define the AWS provider so that Terraform can connect to the correct cloud api services. Terraform uses AWS Provider with proper credentials to connect with Amazon to manage, deploy, update dozens of AWS services.
Previously you learned about the theoretical aspects of what Terraform is and how it works. But before you actually write a Terraform configuration file to create a resource, it is important to know the syntax.
With Terraform, you can simply create the resources using resource blocks or by creating a module (A module is a container for multiple resources that are used together). Let's checkout the syntax.
The below code is a resource block in Terraform where:
The Below code is a module block in Terraform where:
'source' is the value which provides the path to a local directory containing the module's configuration files, or a remote module source that Terraform should download and use.
'version' provides the acceptable version numbers to avoid unexpected or unwanted changes.
Next, some of the Terraform files are JSON compatible, suitable for nested blocks and must have .tf.json format syntax. Let’s check out how the terraform code is declared in the .tf format.
Well, Now you have a sound theoretical knowledge of what Terraform is, its configuration file structure and how they are declared. But before jumping in to learn and use Terraform, you must have terraform installed on your machine.
Installing Terraform on Ubuntu
Before you install your terraform package make sure to update your already existing system packages by running the sudo apt update.
Terraform backend is basically a location where terraform's state file resides. This state file has all the resource details and tracking which were provisioned or will be provisioned via terraform plan or apply command.
There are two types of Backends,
'local' that resides where you run terraform from, it could be Linux/ windows or wherever you run it from and
'remote backend' which is like a URL or may be a different storage location like S3 bucket.
In this tutorial you learnt the basics of Terraform and what you need to create or manage your infrastructure using Terraform.
This is the first blog in our 2-part blog series on Terraform. If you wish to continue reading about Terraform, and how multiple instances can be deployed in one go using Terraform, then click here.
‍
Squadcast is an incident management tool that’s purpose-built for SRE. Your team can get rid of unwanted alerts, receive relevant notifications, work in collaboration using the virtual incident war rooms, and use automated tools like runbooks to eliminate toil.
What you should do now
Schedule a demo with Squadcast to learn about the platform, answer your questions, and evaluate if Squadcast is the right fit for you.
Curious about how Squadcast can assist you in implementing SRE best practices? Discover the platform's capabilities through our Interactive Demo.
Infrastructure as Code provides a convenient way to manage and automate deployments to cloud infrastructure. In this blog, learn how Terraform can be used to perform Infrastructure as Code.
If you are planning to automate your cloud infrastructure then nothing could be better than Terraform. Terraform is the most widely used and popular automation (infrastructure as code) tool that allows you to build and manage infrastructure easily and efficiently.
In this Terraform series, you are going to learn from the ground up what Terraform is and what you need to know to manage and build your infrastructure using Terraform.
Prerequisites
This article will be a step by step guide. If you would like to follow along, be sure to have the following in place:
Terraform - This tutorial will use Terraform v1.0.8 running on Ubuntu 18.04.5 LTS, but any operating system with Terraform should work.
Introduction to Terraform
Terraform is a tool for building, versioning, and updating the infrastructure. It is written in GO Language and the syntax language of configuration files is HCL i.e HashiCorp Configuration Language(much easier than YAML or JSON).
Terraform has been in use for quite a while now. It is an amazing tool to build and change the infrastructure in a very effective and simpler way. It can be used with a variety of cloud providers such as Amazon AWS, Oracle, Microsoft Azure, Google Cloud, and many more. Let's learn more about it.
Key Features of Terraform
Terraform as a tool is a big game changer to manage cloud infrastructure because of the ease of writing code which is such that the same code can be easily made to work with various cloud providers. There are several other key features of Terraform which make this tool so popular and handy. Let's discuss a few of them now.
Infrastructure as a code: Terraform execution and configuration files are written in Infrastructure as a code language - a high-level language which is easy to understand.
Execution Plan: Terraform provides you in depth details about the deployment and resources it will create before deploying the actual code.
Resource Graph: Terraform makes the life of an administrator simple by providing a graphical view of the resources that are currently being provisioned or are already provisioned.
Files and Directories in Terraform
Terraform code consists of Terraform configuration files that follow a standard structure - an arrangement of files and directories that improves code readability. Lets checkout details about these files and folders.
Terraform modules are top-level directories. A single module contains mainly five Terraform configuration files: main.tf, vars.tf, providers.tf, output.tf and terraform.tfvars which are written with .tf format or .tf.json or .tfvars format. These are known as root modules.
The Root module can call other child modules from either local directories or Terraform Registry or from anywhere in the disk
As you can see in the below image there are two child modules - AWS EC2 and AWS S3. Modules containing all the required configurations(main.tf, vars.tf, provider.tf, terraform.tfvars etc) are the ROOT modules for themselves but also acts as child module for the other ROOT module that contains both EC2 and AWS S3.
Now, let's dive into five configuration files that a root module requires.
main.tf → The main.tf file contains the main code that defines which resources you need to create or manage the infrastructure. Below is an example of a main.tf file that creates a resource - 'ec2 instance' under which you need to define:
The resource type that you need to create- "aws_instance".
Arguments containing the values- "ami" and "instance_type" of type string.
Timeout is an argument of type map containing "create" and "delete" values.
vars.tf → The vars.tf contains all the variables that the configuration file (main.tf) references. Below is an example of a vars.tf file that contains variables of different types that you refer to in main.tf, such as:
terraform.tfvars → terraform.tfvars contains the values that terraform uses to replace the variables referred inside main.tf.
output.tf → Terraform output configuration provides the output of AWS resources such as arn or IP address after you execute the terraform apply command. Below is an example of output.tf file that provides the resource outputs such as AWS EC2 instance arn, and public IP address after executing the terraform apply command
provider.tf → The provider.tf file is where you define the AWS provider so that Terraform can connect to the correct cloud api services. Terraform uses AWS Provider with proper credentials to connect with Amazon to manage, deploy, update dozens of AWS services.
Previously you learned about the theoretical aspects of what Terraform is and how it works. But before you actually write a Terraform configuration file to create a resource, it is important to know the syntax.
With Terraform, you can simply create the resources using resource blocks or by creating a module (A module is a container for multiple resources that are used together). Let's checkout the syntax.
The below code is a resource block in Terraform where:
The Below code is a module block in Terraform where:
'source' is the value which provides the path to a local directory containing the module's configuration files, or a remote module source that Terraform should download and use.
'version' provides the acceptable version numbers to avoid unexpected or unwanted changes.
Next, some of the Terraform files are JSON compatible, suitable for nested blocks and must have .tf.json format syntax. Let’s check out how the terraform code is declared in the .tf format.
Well, Now you have a sound theoretical knowledge of what Terraform is, its configuration file structure and how they are declared. But before jumping in to learn and use Terraform, you must have terraform installed on your machine.
Installing Terraform on Ubuntu
Before you install your terraform package make sure to update your already existing system packages by running the sudo apt update.
Terraform backend is basically a location where terraform's state file resides. This state file has all the resource details and tracking which were provisioned or will be provisioned via terraform plan or apply command.
There are two types of Backends,
'local' that resides where you run terraform from, it could be Linux/ windows or wherever you run it from and
'remote backend' which is like a URL or may be a different storage location like S3 bucket.
In this tutorial you learnt the basics of Terraform and what you need to create or manage your infrastructure using Terraform.
This is the first blog in our 2-part blog series on Terraform. If you wish to continue reading about Terraform, and how multiple instances can be deployed in one go using Terraform, then click here.
‍
Squadcast is an incident management tool that’s purpose-built for SRE. Your team can get rid of unwanted alerts, receive relevant notifications, work in collaboration using the virtual incident war rooms, and use automated tools like runbooks to eliminate toil.
What you should do now
Schedule a demo with Squadcast to learn about the platform, answer your questions, and evaluate if Squadcast is the right fit for you.
Curious about how Squadcast can assist you in implementing SRE best practices? Discover the platform's capabilities through our Interactive Demo.
