DevOps(Day-84): Terraform with AWS - Part2

 

  • Task-01: Provision an AWS EC2 instance using Terraform


Task-01: Provision an AWS EC2 instance using Terraform

  • Provision an AWS EC2 instance using Terraform.

  • Create a resource in terraform file to spin the servers in AWS.

  • Count: It specifies the number of EC2 instances to be created.

  • ami: Amazon Machine Image is the ami of the operating system that needs to be flavoured for the instances.

  • Instance_type: It specifies the CPU and storage configurations of EC2 instances.

  • VPC_security_group_ids: We can specify the security group our instances are in, otherwise this will assign by default by creating a new security group.

  • Connection: This block contains the type of connection to be made to the servers, which user to be allowed as a root user, and the private key having access to login to the servers.

  • tags: this will assign the new names to the AWS EC2 instance.

  • Initialise the terraform in the servers to download the required providers.

  • View the plan of Terraform to check the servers spin up with given configurations.

  • Now, apply the terraform file to create the servers.

  • Finally, let's check the console. We can see two servers Server-1 and Server-2 are created.

Thanks for reading my article. Have a nice day.

Comments

Post a Comment

Popular posts from this blog

DevOps(Day-97): Meta-Arguments in Terraform

Image
  TABLE OF CONTENTS Write about meta-arguments and their use in Terraform. Task-01: Meta-Arguments HandsOn Count for-each When you define a resource block in Terraform, by default, this specifies one resource that will be created. To manage several of the same resources, you can use either count or for_each, which removes the need to write a separate block of code for each one. Using these options reduces overhead and makes your code neater. count is what is known as a ‘meta-argument’ defined by the Terraform language. Meta-arguments help achieve certain requirements within the resource block. Write about meta-arguments and their use in Terraform. Meta-arguments in Terraform refer to a set of special arguments that can be used to define how a particular resource or module behaves within a Terraform configuration. These arguments provide additional configuration options and enable fine-grained control over the behaviour of resources or modules. Meta-arguments are prefixed with the...
Read more

DevOps(Day-95): Auto Scaling with Terraform

Image
  TABLE OF CONTENTS Understanding Scaling Pre-requisites Task 1: Create an Auto Scaling Group Task 2: Test Scaling Yesterday, we learned how to AWS S3 Bucket with Terraform. Today, we will see how to scale our infrastructure with Terraform. Understanding Scaling Scaling is the process of adding or removing resources to match the changing demands of your application. As your application grows, you will need to add more resources to handle the increased load. And as the load decreases, you can remove the extra resources to save costs. Terraform makes it easy to scale your infrastructure by providing a declarative way to define your resources. You can define the number of resources you need and Terraform will automatically create or destroy the resources as needed. Pre-requisites Create a  terraform.tf  file declaring the providers to be installed in the system according to the resources required. Create a  provider.tf  file to declare the region. Create a  vp...
Read more

DevOps (Day-1) Introduction

Image
  TABLE OF CONTENTS Infrastructure Automation Why DevOps is Important? What is DevOps? As the name indicates:- Dev + Ops = Development + Operations. Development i) Backend Developers ii) Front-end Developers iii) QA Operations i) System admins ii) Network admins iii) Database admins The practice of operations and development engineers participating together in the entire service lifecycle through a pipeline from design through the development process to production support. This process is known as DevOps. This is a process of automating the whole infrastructure. Now here comes a query, what are we automating? We are automating the whole team's work from the code-building stage to code deployment. Scenario 1:- In a company, there is a project in which developers are writing the code and deploying it to the QA environment frequently for each sprint. This code is then tested by the testing team. Suppose there is a situation of mishap happens where the testing team used the older code ...
Read more