Gain insights into Infrastructure as Code with Terraform, sharpen your skills, and prepare for the HashiCorp Terraform Associate certification in a cloud-agnostic way.

HashiCorp Terraform Certified Associate Preparation Guide.png

Terraform_e.tar.gz

access_key_id

secret_access_key

init

validate

config

needed-copy

not-needed-copy

needed-copy-copy

This course is designed to help learners obtain the Terraform Associate certification from HashiCorp. 

You’ve likely picked up this course because you dabbled in Terraform as a hobbyist or in a
development environment, and you’re excited about the possibilities of deploying Infrastructure 
as Code (IaC). It will enable you to sharpen your skills and prove your knowledge with a certification from HashiCorp. Terraform is an amazing tool to deploy Infrastructure as Code in a cloud-agnostic way. We’re excited to share our accumulated knowledge with you through this course.

HashiCorp Terraform Certified Associate Preparation Guide

# Resource addressing
The resources we create in our Terraform configuration will often be related. For instance, creating a web application that runs on virtual machines might involve a virtual network, virtual machines, network interfaces, firewall rules, and a load balancer. All these resources will refer to each other for their configuration. The load balancer will need to reference the network interfaces on the virtual machines, and the network interfaces will need to reference a subnet on the virtual network. Resource addressing is how we can reference the attributes of a resource within our Terraform configuration.
 
# Format of resource addressing

We’ve already seen several examples of references to both named values and indexes. The general format is different depending on the object type in question. When referring to the value inside a variable, the format is `var.<NAME>`. Resources use the format `resource_type.<NAME>`, followed by the attribute with the value we’d like to retrieve. If we’ve used a for_each or `count` argument to create multiple instances of a resource, then the value returned will be a map or list, respectively.

When referencing a resource, we have access to any arguments we define in the configuration and any attributes that are exported by the resource. A simple example would be retrieving the name of an Azure resource group to be used by another resource.


Learn about resource addressing and resource parameters that can be referenced within a configuration.

Introduction to the Course

Introduction to Infrastructure as Code

Basics of Terraform

Outside the Workflow: Using the Terraform CLI

Terraform Modules

Navigate Terraform Workflow

Implement and Maintain State

Read, Generate, and Modify Configuration

Understand Terraform Enterprise Capabilities

Conclusion

Resource Addressing and Resource Parameters to Connect Resources

Resource addressing