Hover/intellisense appears to use newer AWS schema than local provider version (Terraform 0.12.24 / aws 3.37.0)

[dannyb101]

Extension Version

v2.39.2

VS Code Version

Version: 1.117.0 (Universal)
Commit: 10c8e557c8b9f9ed0a87f61f1c9a44bde731c409
Date: 2026-04-21T16:12:14-07:00
Electron: 39.8.7
ElectronBuildId: 13841579
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

Operating System

macOS Sequoia Version 15.7.5 (24G624)

Terraform Version

Terraform v0.12.24 + provider.aws v3.37.0

Steps to Reproduce

1. Open a Terraform project folder in VS Code that pins AWS provider = 3.37.0.
2. Run terraform init in the project folder.
3. Open Terraform files and trigger hover/completion on AWS resources/attributes (e.g. ElastiCache replication group attributes).
4. Compare extension hover/intellisense behavior vs local schema output.

Expected Behavior

Hover/intellisense should reflect the locally installed/provider-pinned AWS schema (3.37.0) for this module.

Actual Behavior

Hover/intellisense appears to reflect a newer AWS schema (6.x behavior), causing mismatches with 3.37.0-era attributes and suggestions.

Terraform Configuration

provider "aws" {
  profile = "default"
  region = var.aws_region
  version = "= 3.37.0"
}

terraform {
  backend "s3" {
    bucket         = "*******"
    region         = "eu-west-1"
    key            = "*******"
    dynamodb_table = "*******"
    encrypt        = true
  }
}

Project Structure

terraform/
  aws.tf
  backend.tf
  ...

Gist

No response

Anything Else?

• The provider schema is successfully downloaded on init at terraform/.terraform/plugins/darwin_amd64/terraform-provider-aws_v3.37.0_x5

Workarounds

None worked. I tried various versions of the vs code extension and attempting to force the version of terraform-ls

References

No response

Help Wanted

• I'm interested in contributing a fix myself

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment