This document discusses Terraform, an open-source tool that allows users to define and provision infrastructure resources in a declarative configuration file. It summarizes that Terraform allows users to build, change, and destroy infrastructure components like compute instances, storage buckets, and networking through declarative configuration files, enabling an infrastructure-as-code approach that is easy to version, track changes for, and integrate with continuous delivery practices.

1. Marcelo Serpa

2. About me
❏ Software Architect at ilegra
❏ AWS & GCP
❏ Google Cloud Architect Certified
❏ Microservices
❏ Mortal Kombat Player :D
❏ https://github.com/marceloserpa/
❏ https://www.linkedin.com/in/marceloserpa/

3. The old way ...
❏ Management infrastructure using provider UI
❏ Large documentation and configuration drift
❏ Slow process
❏ Error prone

4. Architecture Evolution

5. Complexity is growing

6. What is Terraform?
❏ Build, change and destroy infrastructure
❏ Low-level components: instances, buckets, networking
❏ High-level components: SaaS Feature like Datadog Dashboard, DNS Entries
❏ Declarative (HCL) - infrastructure as code
❏ Easy to versioning and track changes
❏ Continuous Delivery and GitOPS
❏ DRY
❏ Minimal human interaction
❏ Support different providers but using different configuration

7. How it works?

8. Describe infrastructure

9. Execution plan

10. Example: Topology

11. Code
Danger: Security Issue

12. Code

13. > terraform apply