Terraform best practices with examples and argumentsИнфраструктура как код
Anton Babenko is a long time developer, CTO, and tech-lead who is spending a large amount of his time as an open-source contributor to various Terraform & AWS projects, terraform-aws-modules, modules.tf and a few others. The most popular one is where he manages a collection of verified Terraform AWS modules (terraform-aws-modules on GitHub) which is being downloaded more than 1 million times. He also leads AWS, DevOps and HashiCorp User Groups in Norway, organizes DevOpsDays Oslo, and speaks often at various technical meetups and conferences. He is passionate about all-things-cloud and solution architecture combined with automation and scripting.
This talk is for the developers who want to learn best practices in using Terraform at companies and projects of various size (from small to very large), get pros&cons on code structuring, composition. Also, attendees will be able to learn Terraform (and Terragrunt) tricks and gotchas.
It is easy to get started with Terraform to manage infrastructure as code. Just read the documentation on terraform.io, and you are done. Almost.
The harder part begins when infrastructure grows in all directions (several AWS/GCP accounts, regions, teams, projects, environments, external integrations). One of the most frequent questions is "how to structure code".
In this talk, I will explain many of challenges related to that, what works, what does not work, why so, and most importantly I will show all the code which works from small projects to very-large infrastructures (featuring multi-cloud and multi-region setup).
This talk is best suitable for people who have been using Terraform at least for some time and already have practical questions.
All the code and solutions presented at the workshop will be open-sourced.