As DevOps grows, it helps to know about how it works. One of the big things in DevOps is “infrastructure as code”. This means that you treat your infrastructure the exact same as you would treat your application code. So you’ll check it into version control, write tests for it, and make sure that it doesn’t diverge from what you have across multiple environments. Many companies are struggling to manage the cloud infrastructure as they spend too much time and effort to build, configure, and maintain infrastructure manually. With “infrastructure as code” one can easily achieve cloud cost optimization as well as reduction of time and effort put on managing infrastructure. In this blog post, we will go through a recommended plan for creating AWS infrastructure in a highly reusable way using Terraform.

We will create an EC2 instance in AWS. In a production scenario, more than just running instances, we need to address its security properly. We need to have a virtual private cloud, where we can logically isolate our instances and other resources from other virtual networks in the AWS cloud. For this, we make use of Amazon Virtual Private Cloud (VPC) which enables us to create our resources in an isolated private network inside the AWS cloud. in AWS VPC, We have complete control over our virtual networking environment, including selection of our own IP address range, creation of subnets, and configuration of route tables and network gateways. We can use both IPv4 and IPv6 in our VPC for secure and easy access to resources and applications.

#terraform #aws-vpc #aws #devops #cloud