\n<\/em>
\n2) Create a key pair on AWS Management Console or via CLI which will be used for connecting to the instance during the launch
\n<\/em><\/p>\n
Step 1) Install Terraform <\/strong><\/p>\n Step 2) Configure Variables <\/strong><\/p>\n Step 3) Launch Infrastructure<\/strong><\/p>\n Step 4) Push the code to git ( Maintain Versions of Insfrastructure )<\/strong><\/p>\n Let’s break down the steps \ud83d\ude42<\/p>\n You can download it here [js] Terraform is downloaded and installed. Just run to check whether it is installed or not<\/p>\n [js] $ terraform [\/js]<\/p>\n You will get the above output.<\/p>\n Terraform configuration are simple text file in JSON format and has .tf extensions<\/p>\n We’ll create three .tf files<\/p>\n ( we’ll define variables here )<\/p>\n ( will contained details about infrastructure)<\/p>\n (Expected Output)<\/p>\n We will create one terraform.tfvars<\/strong> files which will contain secret informations (access_key\/secret_key) and put this in .gitignore<\/strong><\/p>\n We’ll define variables inside variables.tf file [js] variable "aws_region"{ variable "aws_amis"{ As you can see we are using variables name aws_region and aws_amis with given value.<\/p>\n access_key and secret_key is placed in terraform.tfvars<\/strong> files in below format<\/p>\n \u00a0<\/strong><\/p>\n [js] We have created a key-pair on Management console named “terraform” and downloaded terraform.pem<\/p>\n We’ll define provider\/resources inside main.tf file. [js] resource "aws_security_group" "default"{ ingress{ } connection={ inline=[ You can see in main.tf<\/strong> we have few sections.<\/p>\n 1) provider<\/strong> : defines the provider, In our case its “AWS” Our configuration is complete. Now we’ll check which how terraform builds the resource that we have declared in our configuration files.<\/p>\n for that we have to execute plan command<\/p>\n [js] $ terraform plan [\/js]<\/p>\n This Output show’s that, Terraform will launch a t2.micro EC2 Server with ami-9eaa1cf6.<\/p>\n \u00a0<\/strong><\/p>\n [js] Since we haven’t received any error message while terraform plan [js] Note: We are passing pemfile name and path as an argument ( Recommended ), instead of declaring on using path_value inside variables.tf.<\/p>\n You will get this output if everything goes well. Now on Web Console, You can see a instance is in launching state<\/p>\n1) Install Terraform<\/h3>\n
\nor<\/p>\n
\n$ cd \/opt
\n$ wget
\n$ unzip terraform_0.3.5_linux_amd64.zip
\n$ export PATH=$PATH:\/opt\/terraForm\/
\n[\/js]<\/p>\n![\"terra1\"](\"\/blog\/wp-ttn-blog\/uploads\/2014\/12\/terra1.png\")
<\/a><\/p>\nvariables.tf<\/h3>\n
main.tf<\/h3>\n
output.tf<\/h3>\n
\n
\n<\/strong><\/p>\nvariables.tf<\/h3>\n
\nvariable "access_key"{}
\nvariable "secret_key"{}
\nvariable "key_name"{}
\nvariable "key_path"{}<\/p>\n
\ndescription="Region to Launch Server’s"
\ndefault="us-east-1"
\n}<\/p>\n
\ndefault = {
\nus-east-1="ami-9eaa1cf6"
\n }
\n}
\n[\/js]<\/p>\nterraform.tfvars<\/h3>\n
\naccess_key=AKIAI****************
\nsecret_key=wJalrXUtnFEMI\/********\/bPxRfiCYzEXAMPLEKE
\n[\/js]<\/p>\n
\n
\n<\/strong><\/p>\nmain.tf<\/h3>\n
\nprovider "aws"{
\n region="${var.aws_region}"
\n access_key="${var.access_key}"
\n secret_key="${var.secret_key}"
\n}<\/p>\n
\n name="terraform-sg"
\n description="Created by terraform"<\/p>\n
\n from_port = 22
\n to_port = 22
\n protocol= "tcp"
\n cidr_blocks = ["0.0.0.0\/0"]
\n }
\n ingress{
\n from_port = 80
\n to_port = 80
\n protocol = "tcp"
\n cidr_blocks = ["0.0.0.0\/0"]
\n }<\/p>\n
\nresource "aws_instance" "web"{<\/p>\n
\n user="ubuntu"
\n key_file="${var.key_path}"
\n }
\n instance_type="t2.micro"
\n ami="${lookup(var.aws_amis, var.aws_region)}"
\n key_name = "${var.key_name}"
\n security_groups= ["${aws_security_group.default.name}"]
\n tags{
\n Name="Terraform-EC2"
\n }
\n provisioner "remote-exec"{<\/p>\n
\n "sudo apt-get -y update",
\n "sudo apt-get -y install nginx",
\n "sudo apt-get -y install php5-fpm",
\n "sudo service nginx restart"
\n ]
\n }
\n}
\n[\/js]<\/p>\n
\n2) resource<\/strong> : block defines a resource that exists within the infrastructure. A resource might be a physical component such as an EC2 instance,
\n3) provisioner<\/strong>: User data scripts.<\/p>\n<\/a><\/p>\noutput.tf<\/h3>\n
\nIn output.tf we will be defining the output variables that’ll be displayed after successful launch.<\/p>\n
\noutput "address"{
\n value="${aws_instance.web.public_dns}"
\n }
\n[\/js]<\/p>\nStep 4) Launch Infrastructure<\/h3>\n
\nNow we’ll apply the changes.<\/p>\n
\n$ terraform apply -var ‘key_name=terraform’ -var ‘key_path=~\/terraform\/terraform.pem’
\n[\/js]<\/p>\n
\n<\/a><\/p>\n