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. 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. Even though you can find most of the information online in docs or online articles, in the book such information is well structured and complicated topics are brought one by one without overwhelming the reader with complexity. This book is more than enough to help you set up Terraform in your projects on a decent level and start using it in production.

Currently, this is the best introduction into Terraform that is on the market. It isn't perfect, but this book does a really good job at taking someone who has never installed Terraform or used it and getting them up to what I would call "intermediate" level of knowledge. I actually interviewed for several DevOps jobs that required Terraform experience by solely reading this book and following along with the tutorials. It covers all the main Terraform concepts and I was able to even impress my interviewers based off the knowledge from this book. 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.Since this code comes from a book about Terraform, the vast majority of the code consists of Terraform examples in the by chapter. For example, if you're looking at an example of Terraform code in Chapter 2, you'll find it in the 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. This book helped me understanding how Terraform works and what are the strengths / weaknnesses (immutable, declarative, agentless and so on) 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).

providers (e.g., AWS, Azure, Google Cloud, DigitalOcean) and private cloud and virtualization platforms If you want an other provider, you'll have to manage yourself and probably won't benefit **that much** from the book. You built a module and you want to use it several times—in a loop, essentially—without having to copy and paste the code. However, Terraform 0.12 and below didn’t support count or for_each on module. The solution 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" { Well structured - We start with a “Hello World” example to get the reader up and running, then move onto more complex topics (shared state management, testing, modularization). The book finishes with a discussion of the very important subject of people management with Terraform - how do we introduce Terraform to a team and convince management to adopt this new technology?The rapid evolution of the DevOps industry, though still in its infancy, poses an interesting question. The myriad of tools associated with Terraform has set a precedent, and one can only wonder where the trajectory will take us. Given the ever-evolving nature of technology, this book presents an effective foundation for those wanting to stay ahead of the curve. 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. Maturity. How Terraform has become more stable due to the Terraform 1.0 release, the growth of the community, and the HashiCorp IPO. Static analysis: How to perform other types of automated testing on Terraform code, such as static analysis.

The second ingredient is to strictly limit what the CI server can do once it has authenticated: for example, in the OIDC snippet above, you’ll want to severely limit the permissions in that IAM role. But then how do you handle the admin permissions you need to deploy arbitrary Terraform changes? The emergence of OpenTofu, spearheaded by the Linux Foundation, as an open-source alternative to Terraform, is a testament to the need for flexibility and adaptability in the industry. Personally, I find the creation of this fork a refreshing move, reflecting the community's resilience and adaptability. HashiCorp's recent decisions around Terraform's licensing have been, in my opinion, questionable. Their approach might not have been in the best interest of the broader community. I'm optimistic that the OpenTofu initiative will keep the spirit of open-source and collaboration alive, ensuring the tool's longevity and relevance. Inclusion of problems. I’d love to have an “Extra for Experts” of challenges for readers to solve to solidify their knowledge.

Table of contents

Well written - Brikman is clearly an experienced writer and this practice shows. The book is enjoyable to read while presenting dense technical content. code after it has been written. If you're the one managing infrastructure, deploying code, configuring Update, September 28, 2022: The final version of Terraform: Up & Running, 3rd edition has been published! Grab your copy now! Terraform: Up & Running is now on its 3rd edition; all the code in master is for this edition. If you're looking 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.