Terraform - Up and Running: Writing Infrastructure as Code

Product Information

Therefore, except for a few niche cases, I recommend the cloud native approach. This is also the approach that Terraform is designed for: you can use Terraform with multiple clouds, but you have to write separate code for each cloud, using the providers and resources native to that cloud. Therefore, even for multi-cloud deployments, it’s unusual to build a single Terraform module that deploys into multiple clouds (that is, uses multiple different providers in one module); it’s much more common to keep the code for each cloud in separate modules. In the second part of the series, which will come out when the final version of the 3rd edition is published ( Update, September 28, 2022: the 3rd edition is now published , and the second part of the blog post series is available !), I’ll cover 5 more problems and solutions, including input validation, refactoring, static analysis, policy enforcement, and maturity. Grab a copy of the book to get full access to all of this content! Multiple regions, accounts, and clouds The problem Since this code comes from a book about Terraform, the vast majority of the code consists of Terraform examples in the This is a two part blog post series. In the first part of the series (this blog post), I’ll go into detail on the following 5 problems and their solutions, based on snippets from the 3rd edition of the book: The author describes why and how should one use Terraform, the importance of the Infrastructure as Code in the first chapter. And step by step, chapter by chapter, the author gives the most of best practices of terraform, how to organize your infrastructure code and main problems you may encounter. The chapters explaining terraform are heavily on AWS, some may consider that a thumbsdown for the book, but as the author explained the reason for that, all those examples can be tested on a free tier AWS account, unless it is stated otherwise.

I've been using Terraform for almost two years right now, and I'd recommend this book to anyone who wants to increase their understanding on terraform and its best practices. What I would expect from the author to update in the next version of this book: Just about all of the code examples in the 2nd edition of the book used a single region in a single account of a single cloud (AWS). But what if you wanted to deploy into multiple regions? Or multiple accounts? Or multiple clouds (e.g., AWS, GCP, and Azure)? The solution One thing where I had hoped to get more out of is the "testing" chapter. I'm not sold on the presented approach. Or in other words: the approach presented here seems a lot of effort compared to what I'm currently working on which also works reasonably well (gitops + pre-prod env + terraform.io and inspecting the plan-output in Github PRs). I read the first edition of this book, so the terraform version is a little dated, making the exercises hard to follow at times. Also goes to show how fast terraform is evolving and not even yet hit the first leading major version, I.e., 0.* version only. The other challenge was also the intro of terragrunt, by the author, which made an entry and then disappeared later on, making it hard to follow the tutorial style text. This hands-on-tutorial, now in its 3rd edition, not only teaches you DevOps principles, but also walks you

Table of contents

The positives of the book would be that it covers all the main concepts of Terraform in a very easy-to-read way. Chapter 1 is a solid introduction to Terraform, its purpose, and its history. In chapters 2-5 you will actually follow a general infrastructure buildout from the first line of code, all the way through several refactors. Each refactor adding new features or better structure to the system. Essentially the author introduces a new concept and then shows how to improve our Terraform project by implementing that concept. I think this is a very good teaching method for beginners. The core features of Terraform are explained well and require no previous experience. You’ve now had a small taste of just 5 of the problems that have been solved in the Terraform world in the last few years and are now covered by the 3rd edition of Terraform: Up & Running, including how to work with multiple regions, accounts, and clouds, how to control your provider versions, how to manage secrets securely with Terraform, how to set up a secure CI / CD pipeline, and how to do control logic with modules. Secrets management: examples of using different types of secret management tools (e.g., Vault, KMS, etc) with Terraform. Terraform has become a key player in the DevOps world for defining, launching, and managing infrastructure as code (IaC) across a variety of cloud and virtualization platforms, including AWS, Google Cloud, Azure, and more. This hands-on second edition, expanded and thoroughly updated for Terraform version 0.12 and beyond, shows you the fastest way to get up and running.

I have been using Terraform at work for a couple of weeks. The setup was created by co-workers and I wanted to dive into this book to learn a bit more about TF on top of what I've already learned via d2d work. Yevgeniy Brikman's "Terraform: Up and Running" is a stellar guide to one of the most game-changing tools in the DevOps landscape. The book, deserving of its 5 stars, delves deep into practical examples and offers invaluable tips for creating production-grade code. This ensures that readers not only understand the theory behind Terraform but can also implement best practices with confidence. For instructions on running the code, please consult the README in each folder, and, of course, the Cloud native: With this approach, the idea is to try to use each cloud independently, leveraging its unique services as much as possible. Well written - Brikman is clearly an experienced writer and this practice shows. The book is enjoyable to read while presenting dense technical content.

Update the code to work with the current version of Terraform. Providers are now separated from the main repository and the way terraform init works has changed slightly.

code after it has been written. If you're the one managing infrastructure, deploying code, configuring The entire book has also been updated to mark all input and output variables that could contain secrets with the new sensitive keyword, which was introduced in Terraform 0.14 and 0.15 to tell Terraform to never log these values, as they may contain sensitive data: variable "db_username" {It's a pretty good book to get you started with Terraform. It provides great best practices for using Terraform in your company you couldn't find in one place anywhere else. by chapter. For example, if you're looking at an example of Terraform code in Chapter 2, you'll find it in the I also want to warn readers that the infrastructure in this book is not even close to production-quality. I think it is fine, since this is a book about Terraform and not Cloud Architecture, but it is worth noting. I wish the author had put a little more effort into delineating that. The examples in the book all use the AWS default VPC. Many features of load balancers, networking, and HA are omitted. I think it is ok, since the book is focused on Terraform itself and not the actual systems you are building. But it could give naive readers a false sense of empowerment to go out and deploy this system used in the book.