Book Image

Getting Started with Terraform - Second Edition

By : Kirill Shirinkin
1 (1)
Book Image

Getting Started with Terraform - Second Edition

1 (1)
By: Kirill Shirinkin

Overview of this book

Terraform is a tool used to efficiently build, configure, and improve the production infrastructure. It can manage the existing infrastructure as well as create custom in-house solutions. This book shows you when and how to implement infrastructure as a code practices with Terraform. It covers everything necessary to set up the complete management of infrastructure with Terraform, starting with the basics of using providers and resources. It is a comprehensive guide that begins with very small infrastructure templates and takes you all the way to managing complex systems, all using concrete examples that evolve over the course of the book. The book ends with the complete workflow of managing a production infrastructure as code—this is achieved with the help of version control and continuous integration. The readers will also learn how to combine multiple providers in a single template and manage different code bases with many complex modules. It focuses on how to set up continuous integration for the infrastructure code. The readers will be able to use Terraform to build, change, and combine infrastructure safely and efficiently.
Table of Contents (15 chapters)
Title Page
About the Author
About the Reviewer
Customer Feedback

Counting servers

So far, we have created only one EC2 instance for the web application MightyTrousers. As the popularity of the app increases, a single server can't handle the load properly anymore. We could scale vertically by increasing the instance size, but it would still leave us with a single server that handles all the critical traffic. In a cloud world, you should assume that absolutely every machine you have can be gone at any moment. You should be prepared for worst case scenarios: a distributed denial-of-service (DDoS) attack putting your cluster on its knees, an earthquake destroying the whole data center, an internal AWS outage, and many others.

Thus, not only as a way to scale the infrastructure, but also to make the application highly available, we should increase the number of instances we have. And it's not only about the number of them, but also the location of each of them: keeping 20 instances in a single place still puts you in a situation where the outage of one data...