Providers and Resources

Welcome! Terraform helps you manage your cloud infrastructure using code. But how does it actually talk to cloud providers and define what you want to build?

This lesson introduces two fundamental concepts: Providers and Resources. These are the basic building blocks of every Terraform configuration and crucial for understanding how IaC works.

Think of a Provider as a plugin that allows Terraform to interact with an external service or API. This could be a cloud provider like AWS, Azure, or Google Cloud, or even services like GitHub, Kubernetes, or Datadog.

• Each provider understands the specific API calls needed for its service.
• It translates your desired infrastructure into actions the service can perform.
• You configure providers to tell Terraform which service to use and how to authenticate.

To use a provider, you declare it in your Terraform configuration files using a provider block. This block specifies the provider's name and any configuration settings it needs, such as the region for a cloud provider.

Here's a common example for the AWS provider:

The terraform block's required_providers section is important. It tells Terraform where to find the provider (its source) and which version to use. This ensures consistency and prevents unexpected behavior.

• Source: Specifies the registry path for the provider (e.g., hashicorp/aws).
• Version: Locks the provider version, preventing breaking changes from new releases.
• The provider "aws" block then configures specific settings, like the AWS region for all resources managed by this provider.

A Resource is a block that describes a single component of your infrastructure. This could be a virtual machine (VM), a network, a database, a storage bucket, or even a user account.

• Each resource type is managed by a specific provider (e.g., aws_s3_bucket is managed by the AWS provider).
• You declare the desired state of your resource, and Terraform works to achieve that state.
• Resources have arguments that define their properties (e.g., size, name, location).

You define a resource using a resource block. This block requires two strings:

• The resource type (e.g., aws_s3_bucket).
• A local name (e.g., my_first_bucket) that is unique within your configuration.

The type tells Terraform what kind of infrastructure component it is, and the name gives it a unique identifier for Terraform to track.

Inside a resource block, you specify arguments. These are key-value pairs that define the properties and configuration of the infrastructure component. The available arguments depend on the resource type and its managing provider.

• For an AWS S3 bucket, arguments might include bucket (the unique name), acl (access control list), or tags for labeling.
• Terraform uses these arguments to create or update the resource to match your desired state in the cloud.

Here’s a simple, complete Terraform configuration. It declares the AWS provider and then uses it to create a basic S3 bucket. This single file is all you need to start defining infrastructure!

When you execute Terraform commands, providers and resources play key roles:

• terraform init: Downloads the necessary provider plugins.
• terraform plan: Uses the provider to communicate with the cloud API and determine what changes are needed to achieve the desired resource state.
• terraform apply: Instructs the provider to make those changes to your actual cloud infrastructure.

They are the core interaction points for managing your infrastructure.

You've learned about Providers and Resources. Let's see if you can identify their roles correctly.

Great job! In this lesson, you gained a foundational understanding of the two most important concepts in Terraform:

• Providers: These are the essential plugins that enable Terraform to interact with various cloud services and APIs. You configure them to specify which service to use and how to authenticate.
• Resources: These are the individual infrastructure components you declare in your configuration. They have types and arguments to define their desired state.

These two elements work hand-in-hand to let you define and manage your infrastructure as code efficiently!