Terraform is a GREAT tool, but like a lot of other things in life, it has its pitfalls and bad practices. In this ignite talk, I’ll cover the preliminary practice you should think of in regards to Terraform – Structuring its code base – And explain how this decision has an effect on Terraform Infra & teams scaling, as well as a crucial effect on the core behaviour of Terraform itself.

1. Terraform Practice
Hila Fish
Senior DevOps / Infrastructure Engineer / SRE @ Wix.com
to Enable Infrastructure Scaling

2. Terraform Practices
Hi! I’m Hila Fish
➔ Senior DevOps Engineer / SRE @ Wix.com
➔ 15 years experience
➔ AWS Community Builder,
➔ Hashicorp Ambassador
➔ Conference Core Organizer - DevOpsDays TLV
➔ Lead singer in a cover band
🎤

3. Terraform Practice – Codebase Structure
Structuring your TF code base
How do you
structure TF
code?

4. live
BI
airflow
AWS
Production
/dev/other
team
project
cloud provider
Account
/env
modules
Structuring your TF code base
. . .
IAM
S3-bucket
autoScaling
Terraform Practice – Codebase Structure
region us-east-1

5. 1. Terraform as a Platform
Terraform Practice – Team & Projects Codebase Structure – Why?
• Onboarding all teams - same repo –
Standard for the entire company
• Codeowners usage –
Teams’ autonomy for managing their own infra
• Out of the box:
o (custom) modules to use
o Practices enforcements - tests/checks

6. 2. Small TF States
Terraform Practice – Team & Projects Codebase Structure – Why?
live
BI
airflow
AWS
Production
/dev/other
us-east-1
State file –
Kept in this level

7. Terraform Practices
Code Base
Structure
.
TF as a Platform
.
Small state files

8. Thank
You!
Terraform Practices
hilafish1@gmail.com Twitter: @Hilafish1
Hila Fish, Senior DevOps / Infrastructure Engineer / SRE @ Wix.com