Infraestructura como código (IaC)

Welcome to Infrastructure as Code (IaC)! This lesson explores how to manage and provision your infrastructure using code, rather than manual processes.

Think of it like writing a program for your servers, networks, and databases. It's a fundamental practice in modern DevOps and cloud-native development.

Manually setting up infrastructure is slow, error-prone, and inconsistent. IaC solves these problems!

• Speed: Deploy entire environments in minutes.
• Consistency: Identical setups every time, avoiding 'configuration drift'.
• Version Control: Track changes, collaborate, and revert easily.
• Cost Savings: Optimize resource usage by defining exactly what you need.

There are two main approaches to IaC:

• Declarative: You describe the desired state of your infrastructure. The tool figures out how to get there.
• Imperative: You define the specific steps to take to achieve a state.

Modern IaC tools predominantly use a declarative approach for better maintainability and reliability.

With declarative IaC, you define the 'what', not the 'how'. You simply state what resources you need and their configurations.

For example, you tell the system: "I need 2 web servers of type X, a database, and a load balancer." The IaC tool then provisions these resources, updates them if they don't match, or removes those no longer declared.

Imperative IaC involves writing scripts that execute commands in a specific, sequential order.

For example: "Create server A, then install software X on it, then open port Y."

While powerful for simple tasks, it can be harder to manage complex states and ensure consistency compared to declarative methods, especially in large-scale environments.

Several popular tools help you implement IaC:

• Terraform: A widely-used open-source tool from HashiCorp. It's cloud-agnostic, supporting AWS, Azure, GCP, and many others.
• AWS CloudFormation: Amazon's native IaC service, specifically for managing AWS resources.
• Azure Resource Manager (ARM): Microsoft's native IaC for Azure.
• Ansible, Chef, Puppet: Configuration management tools often used alongside IaC for software installation and system configuration.

Terraform uses HashiCorp Configuration Language (HCL) to define infrastructure. Key components include:

• Providers: Plugins that interact with cloud APIs (e.g., aws, azurerm).
• Resources: Specific infrastructure components you want to manage (e.g., aws_instance, google_compute_network).
• Variables & Outputs: For making configurations dynamic, reusable, and sharing information between modules.

Here's a tiny conceptual Terraform snippet to provision an AWS EC2 instance. Notice how it declares the *desired state* rather than step-by-step instructions.

Using IaC tools typically follows a simple yet powerful workflow:

• plan: Preview the changes your code will make to your infrastructure. This is a crucial safety step to understand potential impacts.
• apply: Execute the changes defined in your code, provisioning or updating resources to match your desired state.
• destroy: Tear down all resources managed by your configuration (use with extreme caution in production!).

Which of the following is NOT a primary benefit of using Infrastructure as Code (IaC)?

You've learned that Infrastructure as Code (IaC) is about managing and provisioning infrastructure through machine-readable definition files. It's a core component of modern DevOps.

IaC brings the benefits of software development (version control, automation, testing) to your infrastructure, leading to faster, more reliable, and consistent deployments. Tools like Terraform and CloudFormation are essential for building and operating scalable SaaS platforms.