JSON configuration alternative in Terraform - Mini Project: Build & Apply

Terraform JSON Configuration Alternative

📖 Scenario: You are setting up a simple cloud infrastructure using Terraform. Instead of using the usual .tf files, you will write the configuration using Terraform's JSON syntax. This helps when you want to generate Terraform configs programmatically or prefer JSON format.

🎯 Goal: Create a Terraform configuration in JSON format that defines a provider and a resource to launch a virtual machine instance with specific properties.

📋 What You'll Learn

Create a JSON object for Terraform configuration

Define the provider block for AWS with region us-east-1

Define a resource block for an AWS EC2 instance named example

Set the instance type to t2.micro and use AMI ID ami-0c55b159cbfafe1f0

Use valid JSON syntax compatible with Terraform

💡 Why This Matters

🌍 Real World

Terraform supports JSON configuration as an alternative to HCL. This is useful when generating configs programmatically or integrating with tools that produce JSON.

💼 Career

Understanding Terraform JSON syntax helps cloud engineers automate infrastructure provisioning and integrate Terraform with other systems.

1

Create the base JSON structure for Terraform

Create a JSON object called terraformConfig with an empty provider and resource keys as empty objects.

Terraform

{
  "provider": {},
  "resource": {}
}
# Your code here

Hint

Start with an object that has provider and resource keys, both set to empty objects.

2

Add AWS provider configuration

Inside the provider object, add an aws key with an object that sets region to "us-east-1".

Terraform

{
  "provider": {
    
  },
  "resource": {}
}
# Add AWS provider with region "us-east-1" inside provider

Hint

Inside provider, add "aws": { "region": "us-east-1" }.

3

Add AWS EC2 instance resource

Inside the resource object, add an aws_instance key. This key should be an object with a key example that contains an object with ami set to "ami-0c55b159cbfafe1f0" and instance_type set to "t2.micro".

Terraform

{
  "provider": {
    "aws": {
      "region": "us-east-1"
    }
  },
  "resource": {
    
  }
}
# Add aws_instance resource named example with ami and instance_type

Hint

Inside resource, add "aws_instance": { "example": { "ami": "ami-0c55b159cbfafe1f0", "instance_type": "t2.micro" } }.

4

Complete the Terraform JSON configuration

Ensure the JSON object has the provider with AWS region us-east-1 and the resource with an aws_instance named example with the specified AMI and instance type. The JSON must be valid and ready for Terraform to use.

Terraform

{
  "provider": {
    "aws": {
      "region": "us-east-1"
    }
  },
  "resource": {
    "aws_instance": {
      "example": {
        "ami": "ami-0c55b159cbfafe1f0",
        "instance_type": "t2.micro"
      }
    }
  }
}
# Verify JSON is complete and valid for Terraform

Hint

Check that all required keys and values are present and the JSON syntax is correct.

Practice

1. What is the main reason to use JSON configuration files in Terraform instead of the usual HCL language?

easy

A. To enable automation and integration with other tools

B. Because JSON files are easier to read for humans

C. To reduce the size of the configuration files

D. Because Terraform does not support HCL anymore

Solution

1. Step 1: Understand Terraform configuration formats

   Terraform supports both HCL and JSON formats for configuration files.

2. Step 2: Identify the benefit of JSON format

   JSON is often used for automation and integration with other tools because it is a widely supported data format.

3. Final Answer:

   To enable automation and integration with other tools -> Option A

4. Quick Check:

   JSON helps automation = C [OK]

Hint: JSON is best for automation and tool integration [OK]

Common Mistakes:

• Thinking JSON is easier for humans to read than HCL
• Believing Terraform no longer supports HCL
• Assuming JSON reduces file size

2. Which of the following is the correct way to start a Terraform JSON configuration file?

easy

A. { "resource": { "aws_instance": { "example": { "ami": "ami-123456", "instance_type": "t2.micro" } } } }

B. { resource: { aws_instance: { example: { ami: "ami-123456", instance_type: "t2.micro" } } } }

C. { "resource": [ { "aws_instance": { "example": { "ami": "ami-123456", "instance_type": "t2.micro" } } } ] }

D. [ "resource": { "aws_instance": { "example": { "ami": "ami-123456", "instance_type": "t2.micro" } } } ]

Solution

1. Step 1: Check JSON syntax rules

   JSON keys and strings must be in double quotes, and objects use curly braces {}.

2. Step 2: Identify correct Terraform JSON structure

   Terraform expects "resource" as a key with nested objects, not arrays or unquoted keys.

3. Final Answer:

   { "resource": { "aws_instance": { "example": { "ami": "ami-123456", "instance_type": "t2.micro" } } } } -> Option A

4. Quick Check:

   Proper JSON syntax with quoted keys = A [OK]

Hint: Always use double quotes for keys and strings in JSON [OK]

Common Mistakes:

• Using unquoted keys in JSON
• Using arrays instead of objects for resources
• Mixing JSON and HCL syntax

3. Given this Terraform JSON snippet:

{
  "variable": {
    "region": {
      "default": "us-west-2"
    }
  },
  "provider": {
    "aws": {
      "region": "${var.region}"
    }
  }
}

What will happen when you run terraform apply?

medium

A. Terraform will deploy resources in the us-west-2 region

B. Terraform will throw an error because variable interpolation is not supported in JSON

C. Terraform will ignore the provider region and use the default AWS region

D. Terraform will deploy resources but with an empty region value

Solution

1. Step 1: Understand variable interpolation in Terraform JSON

   Terraform JSON does not support interpolation syntax like "${var.region}" inside JSON files.

2. Step 2: Identify the error cause

   Using interpolation in JSON causes Terraform to fail parsing or applying the configuration.

3. Final Answer:

   Terraform will throw an error because variable interpolation is not supported in JSON -> Option B

4. Quick Check:

   Interpolation not allowed in JSON = A [OK]

Hint: No interpolation syntax allowed in Terraform JSON files [OK]

Common Mistakes:

• Assuming interpolation works same as HCL
• Thinking Terraform ignores invalid region values
• Believing Terraform defaults region silently

4. You have this JSON Terraform config snippet:

{
  "resource": {
    "aws_instance": {
      "ami": "ami-123456",
      "instance_type": "t2.micro",
      "tags": {
        "Name": "ExampleInstance"
      }
    }
  }
}

When running terraform apply, you get a syntax error. What is the most likely cause?

medium

A. The JSON keys are not properly quoted

B. The "tags" block should be an array, not an object

C. The JSON file is missing a root-level "terraform" key

D. The JSON file uses incorrect nesting for resource blocks

Solution

1. Step 1: Review Terraform JSON resource structure

   Terraform expects resource blocks nested as: resource type -> resource name -> attributes.

2. Step 2: Check the nesting in the snippet

   The snippet places attributes directly under the resource type "aws_instance" without the required instance name (e.g., "example") as an intermediate object key.

3. Final Answer:

   The JSON file uses incorrect nesting for resource blocks -> Option D

4. Quick Check:

   Resource nesting must follow Terraform JSON schema = B [OK]

Hint: Check resource nesting carefully in JSON configs [OK]

Common Mistakes:

• Confusing JSON object vs array for tags
• Expecting a "terraform" root key in JSON
• Not quoting JSON keys properly

5. You want to convert this HCL Terraform config to JSON:

resource "aws_s3_bucket" "bucket" {
  bucket = "my-bucket"
  acl    = "private"
  tags = {
    Environment = "Dev"
    Team        = "Cloud"
  }
}

Which JSON configuration correctly represents this resource?

hard

A. {
"resource": {
"aws_s3_bucket": {
"bucket": "my-bucket",
"acl": "private",
"tags": {
"Environment": "Dev",
"Team": "Cloud"
}
}
}
}

B. {
"resource": [
{
"aws_s3_bucket": {
"bucket": {
"bucket": "my-bucket",
"acl": "private",
"tags": {
"Environment": "Dev",
"Team": "Cloud"
}
}
}
}
]
}

C. {
"resource": {
"aws_s3_bucket": {
"bucket": {
"bucket": "my-bucket",
"acl": "private",
"tags": {
"Environment": "Dev",
"Team": "Cloud"
}
}
}
}
}

D. {
"resources": {
"aws_s3_bucket": {
"bucket": {
"bucket": "my-bucket",
"acl": "private",
"tags": {
"Environment": "Dev",
"Team": "Cloud"
}
}
}
}
}

Solution

1. Step 1: Understand Terraform JSON resource format

   Terraform JSON uses "resource" (singular) as the root key with nested resource type and name.

2. Step 2: Compare options for correct keys and structure

   { "resource": { "aws_s3_bucket": { "bucket": { "bucket": "my-bucket", "acl": "private", "tags": { "Environment": "Dev", "Team": "Cloud" } } } } } correctly uses "resource" with nested "aws_s3_bucket" and resource name "bucket" with attributes.

3. Final Answer:

   { "resource": { "aws_s3_bucket": { "bucket": { "bucket": "my-bucket", "acl": "private", "tags": { "Environment": "Dev", "Team": "Cloud" } } } } } -> Option C

4. Quick Check:

   Correct root key and nesting = D [OK]

Hint: Use singular "resource" key with nested type and name [OK]

Common Mistakes:

• Using "resources" instead of "resource"
• Using arrays instead of objects for resources
• Incorrect nesting of resource name and attributes