Terraform - Up and Running: Writing Infrastructure as Code

Product Information

AWS examples only. Minor nit here, but it’s kind of a bummer that the examples in the book and on github are aws only. I can’t blame the author here, since the point is Terraform, not your favorite provider X. 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. The book does a very, very solid job of teaching you how to use terraform right and not mess with your state. However there is another approach presented on how to prevent state file concurrency issues by using a CI to apply server provisioning. Of course this is limited to good will and sanity of other team members still not running terraform apply by themselves since I am not aware of an option preventing terraform users of running apply at all. your infrastructure as code and to deploy and manage that infrastructure across a variety of public cloud 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" {

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. It's one of the most prospering books written about Terraform. Although it's based on Terraform version 0.8, and a lot of things has changed since then, still the examples in the book hold the truth. Moreover, the examples provided in the book are also updated day by day, they force the correct version of terraform to be used. 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? 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.

All the code is in the code folder. The code examples are organized first by the tool or language and then 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 But moving aside from small differences the book is very solid in regards of presenting you practical problems of creating and provisioning environments. Although for "content digestibility", they're greatly simplified compared to real staging/production and etc environments, they present the actual problems of how to use terraform at first, from syntax, declarative resources approach, using data/output/resource/var/module, procedural-like constructs, workflow and reusability.

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. code after it has been written. If you're the one managing infrastructure, deploying code, configuringThis book is the fastest way to get up and running with Terraform, an open source tool that allows you to define Well written - Brikman is clearly an experienced writer and this practice shows. The book is enjoyable to read while presenting dense technical content. 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: through code examples that you can try at home. You'll go from deploying a basic "Hello, World" Terraform