Solution skill
Terraform: "Unsupported argument" and "Unsupported block type" are version or typo problems
Complete solution
These errors name the exact argument and resource. Nine times in ten the provider version does not have that argument yet, or the name is misspelled. Teaches the two-minute check.
TL;DR: These errors name the exact argument and resource. Nine times in ten the provider version does not have that argument yet, or the name is misspelled. Check the provider version in the lock file against the provider docs for that argument. Check spelling against the docs, including underscores vs hyphens and singular vs plural block names.
The error
Error: Unsupported argument
on main.tf line 12, in resource "aws_instance" "web":
12: new_feature_flag = true
An argument named "new_feature_flag" is not expected here.What you are seeing
Error: Unsupported argument
on main.tf line 12, in resource "aws_instance" "web":
12: new_feature_flag = true
An argument named "new_feature_flag" is not expected here.First response
- Check the provider version in the lock file against the provider docs for that argument. "Not expected here" most often means "added in provider v5.40 and you have v5.31". The fix is a version bump, not config creativity.
- Check spelling against the docs, including underscores vs hyphens and singular vs plural block names. Copy the argument name from the docs page, not from memory.
- Check you are in the right resource or block. Arguments valid in one resource are not valid in a similar-looking one, and data sources accept a subset of the resource's arguments.
Rules for agents
- When the docs say the argument exists and your version is current, verify the docs version matches your provider version. Registry docs default to the latest release.
- Do not work around with provisioners or null resources. If the provider lacks the argument, the right moves are: upgrade the provider, or accept the limitation and document it.
terraform validatecatches these without any cloud access. Run it before plan in every workflow; it is the cheapest check you have.- After a provider upgrade that adds the argument, remember
init -upgradeactually installs the new version. Editing the constraint alone changes nothing.
When to use this
- You are seeing this exact error message; match the block above, not just part of it.
- The failing call matches the scenario in the title: Terraform.
- You want the fastest verified fix before digging through logs.
When not to use this
- Your error text differs from the block above; close cousins often have different causes.
- The stack trace points at a different component than the one in the title.
- You already applied this fix and the error persists; look for a second cause instead of reapplying.
Evidence
terraform validate checks configuration validity without cloud access; provider docs list per-argument availability by version. Verified against live docs 2026-09-26. Verified against live docs 2026-09-26.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_kTN0h047sRO4-qJIh1Juxw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Terraform: "Unsupported argument" and "Unsupported block type" are version or typo problems <span>— Vectle</span></a>