The document discusses automating a web application firewall (WAF) using Terraform. It introduces the presenter, Avinash Jain, and his background in security. It then explains why infrastructure automation is important by describing the manual process used in the past. Terraform is introduced as an infrastructure as code tool that allows validating changes through code reviews and automating the entire provisioning and deployment process. Key features of Terraform that are highlighted include representing infrastructure as code, reusability, and versioning changes through commit logs.

1. Automating WAF using Terraform
(Part 1)
- Avinash Jain
@logicbomb_1
Null Meetup - Aug’19

2. Automating WAF using Terraform (Part 1)
Null Meetup - Aug’19

3. $ whoami
> Avinash Jain, a.k.a logicbomb_1 (because logicbomb was already
taken 🤬).
> 4+ years of experience in Information Security.
> Currently working at Grofers as a Lead Infrastructure Security
Engineer.
> Previously worked in MakeMyTrip and Expedia.
> Cyber Security Speaker, A blogger.
> Part time BugBounty Hunter.
> Acknowledged by Google, NASA, Cern.EU, and some top companies.

4. $ whoami(contd.)

5. Why Terraform?
> A long time ago, in a data center far, far away, an ancient group of powerful
beings known as sysadmins used to deploy infrastructure manually.
> Every server, every route table entry, every database configuration, and
every load balancer was created and managed by hand.

6. Why Terraform (contd.)?
> It was a dark and fearful age: fear of downtime, fear of accidental
misconfiguration, fear of slow and fragile deployments, and fear of what would
happen if the sysadmins fell to the dark side (i.e. took a vacation).
> The good news is that thanks to the DevOps Rebel Alliance, we now have a
better way to do things:Infrastructure-as-Code (IAC).

7. What is Terraform?

8. Why Terraform rocks?
> Automate entire provisioning and deployment process
> Validate each infrastructure change through code reviews
and automated tests.
You can -

9. Why Terraform rocks (contd.)?
> Represent the state of your infrastructure in source files
that anyone can read rather than in a sysadmin’s head
> Create (or buy) a library of reusable, documented, battle-
tested infrastructure code that makes it easier to scale and
evolve your infrastructure.
> Store those source files in version control, which means
the entire history of your infrastructure is now captured in the
commit log, which you can use to debug problems, and if
necessary, roll back to older version.
You can -

10. Terraform Architecture

11. 3’s important TFs
> provider.tf
> variable.tf
> main.tf

12. Time for live demo

14. Thank You!
Avinash Jain
Twitter: https://twitter.com/logicbomb_1
LinkedIn: https://www.linkedin.com/in/avinashjain619/
Medium: https://medium.com/@logicbomb_1
Email: avinashjain030193@gmail.com