code after it has been written. If you're the one managing infrastructure, deploying code, configuring For instructions on running the code, please consult the README in each folder, and, of course, the

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. 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. To deploy into multiple clouds, you create multiple copies of different providers. Readers of the first two editions of this book often asked for examples of how to work with multiple clouds (e.g., AWS, Azure, GCP), but I struggled to find an example where it was practical to do this in a single module. Here’s why:The negatives that I would identify would be that it is very front-heavy. Chapters 1-5 are pure gold. Chapter 6 is decent, and the last two chapters (7-8) are a mess. As others have pointed out, this book uses an older version of Terraform and several breaking changes have occurred. But I was still able to follow along. I assume the author will release a 3rd edition soon which should implement the new version 1 of Terraform which should be more stable going forward.

providers (e.g., AWS, Azure, Google Cloud, DigitalOcean) and private cloud and virtualization platforms 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 AWS is the provider of choice and you'll see a lot of AWS lingo which is also explained. Familiarity is a plus, but not required,The code examples on Github are very clear, I found myself lost just following along in the book. I highly recommend that readers use the code examples while working through the book.

Update, September 28, 2022: The final version of Terraform: Up & Running, 3rd edition has been published! Grab your copy now!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. Transparent portability: With this approach, the idea is to try to use all the clouds as one unified computing platform, abstracting away all the differences between cloud providers to make it easier to migrate a workload from one cloud to the other. 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. 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? Maturity. How Terraform has become more stable due to the Terraform 1.0 release, the growth of the community, and the HashiCorp IPO.