Terraform level 1 - 9 Create EBS Volume Using Terraform problem

rwobben · October 23, 2025, 6:05am

What went wrong here :

raymond.baoly · October 23, 2025, 7:02am

Hi @rwobben

I’ve just checked, and it’s working properly on my end. Please try again and use availability_zone = “us-east-1a”.

rwobben · October 23, 2025, 11:41am

here it is still not working

Still got the message that ```
Resources have not been created using ‘Terraform’.

rwobben · October 23, 2025, 12:18pm

with availability_zone = “us-east-1a” is it working

So I think the text in the challenge needs to be adapted because there is stated

availability_zone = “us-east-1”

Srikanth_Reddy · October 23, 2025, 12:21pm

@rwobben one difference that I see is the value that you’ve passed for the availability_zone field.

Each Region has multiple, isolated locations known as Availability Zones . The code for an Availability Zone is its Region code followed by a letter identifier. For example, us-east-1a .

Have you checked if the ebs volume got created in the first place after running terraform apply?

MIQDAD · October 29, 2025, 6:15am

refer to my repo for solution

github.com

MiqdadProjects/kodekloud-terraform-solutions/blob/main/TASK09/Task-9-Create-EBS-Volume.md

```markdown
# 🌟 Task 9 - Create EBS Volume Using Terraform

## 📌 Task Description

The **Nautilus DevOps team** is strategizing the migration of a portion of their infrastructure to the **AWS cloud**. Recognizing the scale of this undertaking, they have opted to approach the migration in incremental steps rather than as a single massive transition. To achieve this, they have segmented large tasks into smaller, more manageable units.

This granular approach enables the team to execute the migration in gradual phases, ensuring smoother implementation and minimizing disruption to ongoing operations. By breaking down the migration into smaller tasks, the Nautilus DevOps team can systematically progress through each stage, allowing for better control, risk mitigation, and optimization of resources throughout the migration process.

**Requirements:**
- Name of the volume should be **`devops-volume`**
- Volume type must be **`gp3`**
- Volume size must be **`2 GiB`**
- Ensure the volume is created in **`us-east-1`**
- The Terraform working directory is **`/home/bob/terraform`**
- Create the **`main.tf`** file (do not create a different .tf file)

👉 **Your task:** Create an EBS volume using Terraform to provide persistent block storage for EC2 instances during the infrastructure migration.

💡 **Note:** EBS volumes provide durable, high-performance block storage that can be attached to EC2 instances.

This file has been truncated. show original

anantm · April 22, 2026, 11:04pm

Any idea why I am getting this error even though resource is created using terraform.

rob_kodekloud · April 22, 2026, 11:13pm

I thiink your problem is that you’re passing “us-east-1” – which is a region – using a flag that expects an availability zone (e.g., “us-east-1a”, “us-east-1b”, etc.). Try doing that – if you read the thread you just added to, you’ll see this is a recurring problem.

anantm · April 22, 2026, 11:36pm

Thanks Rob.

I realized the issue after posting this message. If you see the command line it says that apply complete and resource is created.

anantm · April 23, 2026, 12:11am

I see the lab is using 5.91.0 terraform provider, where as the latest is 6.28.0. I suspect this could be a defect in this version. I wonder if resource creation fails when we use the latest provider.

rob_kodekloud · April 23, 2026, 12:13am

I’m not sure if that’s really a bug, per se: using a region when you’re asked for an availability zone is certain a user error; I’d guess that how terraform’s system respond to this kind of error would be somewhat unpredictable.

MIQDAD · April 23, 2026, 6:34am