{"id":1491,"date":"2022-06-16T09:52:26","date_gmt":"2022-06-16T09:52:26","guid":{"rendered":"https:\/\/www.checkmateq.com\/blog\/?p=1491"},"modified":"2023-08-07T07:39:16","modified_gmt":"2023-08-07T07:39:16","slug":"instance-using-terraform","status":"publish","type":"post","link":"https:\/\/www.checkmateq.com\/blog\/instance-using-terraform","title":{"rendered":"Deploy AWS ec2 Instance using Terraform"},"content":{"rendered":"

Terraform<\/strong> is an open-source infrastructure<\/a> as code tool to automate and manage your cloud<\/a> infrastructure, it uses a declarative language means you just give what you want and terraform will take care of the steps to get it done, you can version, reuse, and share these files, in this blog we will learn how to launch an ec2 instance in AWS using terraform configuration files.<\/p>\n

I am going to use an already launched AWS ec2 instance to launch a new instance with terraform, for this the instance used should have permission to do the same which can be done by attaching a IAM role to the instance<\/p>\n

Step-1: Creating IAM role with AmazonEC2FullAccess to Launch AWS ec2 instances.<\/strong><\/h3>\n

Create a IAM role and with policy AmazonEC2FullAccess, on your AWS web console search for IAM.<\/p>\n

\"\"<\/p>\n

on the left plane click on Roles<\/strong> under Access management\u00a0<\/strong>then click on create role.<\/p>\n

\"\"<\/p>\n

Select “AWS<\/a>” service for “Select type of trusted entity” , EC2 for “Choose a use case”\u00a0 then click on next.<\/p>\n

\"\"<\/p>\n

search for AmazonEC2FullAccess\u00a0<\/strong>policy and select it and click “Next”<\/p>\n

\"\"<\/p>\n

then give a meaningful name for the role you are creating, check the details\u00a0 add tags if required scroll down and click on “create role”<\/p>\n

\"\"<\/p>\n

Check this blog to know the steps for launching a ec2 instance<\/a> , and use below commands to install terraform<\/p>\n

Installing Terraform<\/strong><\/h3>\n

execute below command to install yum-config-manager<\/p>\n

sudo yum install -y yum-utils<\/pre>\n
your machine may not have terraform repository\u00a0 add it using yum-config-manager, use below commands for this<\/p>\n
sudo yum-config-manager --add-repo https:\/\/rpm.releases.hashicorp.com\/RHEL\/hashicorp.repo<\/pre>\n
\"\"<\/p>\n
Execute below command to install terraform<\/p>\n
sudo yum -y install terraform<\/pre>\n
Attaching IAM role to ec2 instance\u00a0<\/strong><\/h3>\n
Go to your ec2 instances select the instance which has terraform installed in it.<\/p>\n
\"IAM\"<\/p>\n
Click on Security <\/strong>under Actions<\/strong> and click on modify IAM role.<\/p>\n
\"\"<\/p>\n
Select the IAM role that you have created and click on Update IAM role<\/strong><\/p>\n
\"\"<\/p>\n
 <\/p>\n
Step-3: Create Terraform files to launch an ec2 instance<\/strong><\/h3>\n
All the terraform files should be saved with “.tf” extension like “provider.tf”, syntax used in terraform configuration files in this blog\u00a0 is called as HashiCorp Configuration Language , HCL is human readable and machine friendly, terraform can also read JSON configurations.<\/p>\n
On your ec2 instance create a folder for your Terraform files and navigate to it, use below commands on your terminal.<\/p>\n
mkdir project-ec2\r\ncd project-ec2\r\n<\/pre>\n
mkdir\u00a0<\/strong>is a command used to create directories<\/p>\n
cd\u00a0<\/strong> is used to change the working directory.<\/p>\n
we will\u00a0 create 3 files variable.tf, provider.tf, main.tf, follow below process.<\/p>\n
create variable.tf<\/strong> and copy below code to the file, please change the highlighted things as per your requirements and changing the value of variable key_name<\/strong> is must as key1\u00a0<\/strong>is the name of the key pair that I already have.<\/p>\n
variables.tf<\/strong><\/h3>\n
variable \"aws_region\" {\r\n  description = \"AWS region in which I want to deploy resources.\"\r\n  default = \"ap-south-1<\/strong>\"\r\n}\r\n\r\nvariable \"key_name\" {\r\n  description = \" credentials keys to connect to ec2 instance\"\r\n  default = \"key1<\/strong>\"\r\n}\r\n\r\nvariable \"instance_type\" {\r\n  description = \"instance type for ec2\"\r\n  default = \"t2.micro<\/strong>\"\r\n}\r\n\r\nvariable \"security_group\" {\r\n  description = \"Name of security group\"\r\n  default = \"my-Securitygroup<\/strong>\"\r\n}\r\n\r\nvariable \"tag_name\" {\r\n  description = \"Tag Name of for Ec2 instance\"\r\n  default = \"my-ec2-instance\"\r\n}\r\nvariable \"ami_id\" {\r\n  description = \"AMI ID for RHEL Ec2 instance\"\r\n  default = \"ami-05c8ca4485f8b138a<\/strong>\"\r\n}\r\n<\/pre>\n
\u00a0variable.tf<\/strong> file where you will give all the details that you will use to launch a instance like ami, region ,security group, instance type, tags ,you can also give this details directly in the implementation file\u00a0 where you declare the resources you want to deploy but its not recommended to hard code all the details, creating a separate variable file helps easily change the configuration any time with out modifying the main implementation file.<\/p>\n
As you can see above syntax each input variable must be declared with a variable block and name for variable is given after the key word variable<\/strong> ,each variable name must be unique, description\u00a0<\/strong>and default\u00a0<\/strong>are arguments I used for variable declaration.<\/p>\n
description <\/strong>: is basically like a documentation for the variable.<\/p>\n
default:\u00a0<\/strong>when given as default variable is considered as optional and only used if no value is given when running terraform.<\/p>\n
Now create a file named provider.tf<\/strong> and copy below given syntax to it and save.<\/p>\n
provider.tf\u00a0<\/strong><\/h3>\n
provider \"aws\" {\r\n  region = var.aws_region\r\n}\r\n<\/pre>\n
Here I gave details of\u00a0 provider(AWS)\u00a0<\/a> and the AWS region where I want to deploy resources , Terraform uses plugins to communicate with cloud providers and other API’s to deploy resources, here we are giving details of which plugin to use, below main.tf\u00a0<\/strong> is the main implementation file to launch where I declared all the resources to be deployed.<\/p>\n
then create a file main.tf\u00a0 <\/strong>here you will declare the resources that you want to deploy, you can use any meaningful name but should be with extension .tf<\/strong><\/p>\n
main.tf<\/strong><\/h3>\n
#Create security group with firewall rules<\/strong>\r\nresource \"aws_security_group\" \"securitygroup-1\" {\r\n  name = var.security_group\r\n  description = \"security group for instance\"\r\n\r\n#inbound<\/strong>\r\ningress {\r\n  from_port = 8080\r\n  to_port = 8080\r\n  protocol = \"tcp\"\r\n  cidr_blocks = [\"0.0.0.0\/0\"]\r\n }\r\n\r\ningress {\r\n  from_port = 22\r\n  to_port = 22\r\n  protocol = \"tcp\"\r\n  cidr_blocks = [\"0.0.0.0\/0\"]\r\n }\r\n\r\n# outbound\u00a0<\/strong>\r\negress {\r\n  from_port = 0\r\n  to_port = 65535\r\n  protocol = \"tcp\"\r\n  cidr_blocks = [\"0.0.0.0\/0\"]\r\n }\r\n\r\ntags= {\r\n Name = var.security_group\r\n }\r\n}\r\n\r\n#declaration to launch instance<\/strong>\r\n\r\nresource \"aws_instance\" \"myFirstInstance\" {\r\n  ami = var.ami_id\r\n  key_name = var.key_name\r\n  instance_type = var.instance_type\r\n  security_groups= [var.security_group]\r\n  tags= {\r\n    Name = var.tag_name\r\n  }\r\n}\r\n<\/pre>\n
Let’s understand the resource\u00a0<\/strong>block first.<\/p>\n
resource “resource key word<\/strong>” “resource name to use across terraform module<\/strong>“{<\/p>\n
here give your resource attributes required to provision it…..<\/p>\n
}<\/p>\n
resource key word: <\/strong>each resource in AWS will have a unique key word , for example “aws_instance” is key word for AWS EC2 instance use the keyword of the resource that you want to deploy.<\/p>\n
resource name to use across terraform module:\u00a0<\/strong>name you give here is only to use across terraform module, it has no scope out side the module.<\/p>\n
In above given main.tf<\/strong> file I am creating a security group to attach it for the instance where I am opening ports 22,8080 to be accessed from any where[0.0.0.0\/0] and outbound to any port starting from port 0(zero) to 65535 and giving a tag with key Name <\/strong>and value it is given from variable.tf<\/strong> file using var.security_group ,to use a variable declared in variable file use var.variable name.<\/strong><\/p>\n
Step-3: Terraform commands to deploy resources\u00a0<\/strong><\/h3>\n
After creating all 3 files , now use below commands to deploy your resources<\/p>\n
Use below command to initialize provider plugins.<\/p>\n
terraform init<\/pre>\n
above command is you used to initialize a directory that containing terraform files, it initializes provider plugins ,This is the first command that you have to run after creating a new terraform file in your directory.<\/p>\n
\"\"<\/p>\n
 <\/p>\n
Terraform command to validate configuration files<\/strong><\/h3>\n
terraform validate<\/pre>\n
terraform validate\u00a0<\/strong>command will validate configuration files for syntactical errors.<\/p>\n
\"\"<\/p>\n
 <\/p>\n
Command to check what resources are to be created<\/strong><\/h3>\n
terraform plan<\/pre>\n
terraform plan\u00a0<\/strong>will evaluate the desired state of resources declared and compares it with the current state in your infrastructure and give a complete output what it is going to do based on your configuration files , it does not create or destroy any resource it only gives the plan.<\/p>\n
\"\"<\/p>\n
 <\/p>\n
Command to deploy your Resources<\/strong><\/h3>\n
terraform apply<\/pre>\n
terraform apply\u00a0<\/strong>will do plan\u00a0<\/strong>same as the terraform plan does and then carries out changes according to the plan using appropriate API’s for each resource, checks the details and press yes\u00a0<\/strong>when it prompts as shown in below image.<\/p>\n
\"\"<\/p>\n
sample final output for terraform apply\u00a0<\/strong>will as given below if it’s successfully done.<\/p>\n
\"\"<\/p>\n
 <\/p>\n
Please contact<\/a> with our technical consultants to discuss cloud<\/a> infrastructure engineering and SaaS based product development strategies.<\/p>\n","protected":false},"excerpt":{"rendered":"
Terraform is an open-source infrastructure as code tool to automate and manage your cloud infrastructure, it uses a declarative language means you just give what you want and terraform will take care of the steps to get it done, you can version, reuse, and share these files, in this blog we will learn how to … Continue reading “Deploy AWS ec2 Instance using Terraform”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":1541,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[3,2,12,7,11,23,16,14],"_links":{"self":[{"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/posts\/1491"}],"collection":[{"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/comments?post=1491"}],"version-history":[{"count":32,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/posts\/1491\/revisions"}],"predecessor-version":[{"id":4306,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/posts\/1491\/revisions\/4306"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/media\/1541"}],"wp:attachment":[{"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/media?parent=1491"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/categories?post=1491"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/tags?post=1491"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}