Terraform: Up & Running: Writing Infrastructure as Code

Livro bem básico e 100% voltado a AWS. Me ajudou em algumas dúvidas, mas conteúdo mais profundo, não. Esperava mais por ser O'Reilly

Highly recommend if your are looking for a good introduction to Terraform, good examples of the main concepts, easy to follow and well explained commands. Also this will help you to much in the certification exam.

This is a great book. Like most of the "Up & Running" book series, it's not an exhaustive reference to everything you'd ever need to know about Terraform – but it offers a great intro to the essentials (how TF works, how to use it individually or in a team workflow, etc.). The book offers plenty of practical real-world examples throughout the book, which start simple and get progressively more advanced (with clear code samples, diagrams, etc.).One more thing I enjoyed about this book is that Brikman does a nice job of not just explaining the mechanics of TF itself, but shares plenty of background and insight into the broader worlds of Infrastructure as Code (IaC) and DevOps in general (with tips, best practices, gotchas, real world stories, etc.).Final word: This book won't teach you everything about Terraform, but it will send you off to a great start.

It seems like 1/3 of all string-type fields in provided code in this book are populated with something totally useless like: "example", "terraform-up-and-running", "..." (yes, even dot-dot-dot) - this is a great opportunity clarify what an abstruse variable is, its function, even give clarity on an example, but instead, far too often, the author gives you something completely worthless like "example". I know Its an example - can you give me something useful with it?p. 99:resource "aws_db_instance" "example" {identifier_prefix = "terraform_up_and_running"who can use their context clues to tell me what the identifier prefix is, how it's used, how it effects the example, and naming convention/strategy? (And no, its not covered in the text) If you can, you're a greater man that I.Besides this time-consuming trip to other docs, this is a pretty good book - I do read the occausional topic and emerge with a shaky understanding, but I am not certain I can fault the book for that. I can certainly fault it for missed naming opportunities.

teaches things from the ground up and ties it together on how to run things in prod as a team.I will buy v3 aswell, which will come in nov. and reread