Book Image

Infrastructure as Code for Beginners

By : Russ McKendrick
4 (1)
Book Image

Infrastructure as Code for Beginners

4 (1)
By: Russ McKendrick

Overview of this book

The Infrastructure as Code (IaC) approach ensures consistent and repeatable deployment of cloud-based IaaS/PaaS services, saving you time while delivering impeccable results. Infrastructure as Code for Beginners is a practical implementation guide that helps you gain a clear understanding of the foundations of Infrastructure as Code and make informed decisions when implementing it. With this book, you’ll uncover essential IaC concepts, including planning, selecting, and implementing the right tools for your project. With step-by-step explanations and real-world examples, you'll gain a solid understanding of the benefits of IaC and the scope of application in your projects. You'll learn about the pros, cons, and best practices of different IaC tools such as Terraform and Ansible, and their use at different stages of the deployment process along with GitHub Actions. Using these tools, you'll be able to design, deploy, and secure your infrastructure on two major cloud platforms, Microsoft Azure and Amazon Web Services. In addition, you'll explore other IaC tools such as Pulumi, AWS CloudFormation, and Azure Bicep. By the end of this book, you’ll be well equipped to approach your IaC projects confidently.
Table of Contents (15 chapters)
1
Part 1: The Foundations – An Introduction to Infrastructure as Code
5
Part 2: Getting Hands-On with the Deployment
9
Part 3: CI/CD and Best Practices

Terraform – reviewing the code and deploying our infrastructure

As we did a deep dive into Terraform in Chapter 4, Deploying to Microsoft Azure, we aren’t going to dig too deep into the code here, and instead will just highlight any considerations we need to make when targeting AWS or if there is a function we didn’t use when deploying our workload to Microsoft Azure.

Walk-through of Terraform files

What follows is a walk-through of each of the Terraform files. Just as we did for Microsoft Azure, I have grouped each logical group of resources in its own .tf file.

Setup

This is not too dissimilar to the one we defined for Azure. There are a few obvious differences – the biggest of which is that we are using the AWS provider:

    aws = {
      source  = "hashicorp/aws"
      version = "~> 4.0"
    }

Also, we...