aws: Error: Pre-built provider information not found

[hinling-blisspoint]

Expected Behavior

cdktf init --template="typescript" --providers="aws" initialized with the typescript project skeleton.

Actual Behavior

Error out with Error: Pre-built provider information not found

Steps to Reproduce

1. npm install -g cdktf-cli && npm install -g cdktf
2. In an empty dir, run cdktf init --template="typescript" --providers="aws"
   Here's the log:

cdktf init --template="typescript" --providers="aws"
? Project Name dd_alert_forwarder
? Project Description A simple getting started project for cdktf.
? Would you like to use Terraform Cloud? yes

Detected Terraform Cloud token.

We will now set up Terraform Cloud for your project.

? Terraform Cloud Organization Name <redacted>

We are going to create a new Terraform Cloud Workspace for your project.

? Terraform Cloud Workspace Name dd_alert_forwarder
? Do you want to start from an existing Terraform project? no

Setting up a Cloud Backend for your project.
? Do you want to send crash reports to the CDKTF team? Refer to 
https://developer.hashicorp.com/terraform/cdktf/create-and-deploy/configuration-file#enable-crash-reporting-for-the-cli for more information yes

Generating Terraform Cloud configuration for 'redacted' organization and 'dd_alert_forwarder' workspace.....

added 2 packages, and audited 102 packages in 5s

28 packages are looking for funding
  run `npm fund` for details

1 low severity vulnerability

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported

added 325 packages, and audited 427 packages in 38s

60 packages are looking for funding
  run `npm fund` for details

1 low severity vulnerability

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
========================================================================================================

  Your CDKTF TypeScript project is ready!

  cat help                Print this message

  Compile:
    npm run get           Import/update Terraform providers and modules (you should check-in this directory)
    npm run compile       Compile typescript code to javascript (or "npm run watch")
    npm run watch         Watch for changes and compile typescript in the background
    npm run build         Compile typescript

  Synthesize:
    cdktf synth [stack]   Synthesize Terraform resources from stacks to cdktf.out/ (ready for 'terraform apply')

  Diff:
    cdktf diff [stack]    Perform a diff (terraform plan) for the given stack

  Deploy:
    cdktf deploy [stack]  Deploy the given stack

  Destroy:
    cdktf destroy [stack] Destroy the stack

  Test:
    npm run test        Runs unit tests (edit __tests__/main-test.ts to add your own tests)
    npm run test:watch  Watches the tests and reruns them on change

  Upgrades:
    npm run upgrade        Upgrade cdktf modules to latest version
    npm run upgrade:next   Upgrade cdktf modules to latest "@next" version (last commit)

 Use Providers:

  You can add prebuilt providers (if available) or locally generated ones using the add command:
  
  cdktf provider add "aws@~>3.0" null kreuzwerker/docker

  You can find all prebuilt providers on npm: https://www.npmjs.com/search?q=keywords:cdktf
  You can also install these providers directly through npm:

  npm install @cdktf/provider-aws
  npm install @cdktf/provider-google
  npm install @cdktf/provider-azurerm
  npm install @cdktf/provider-docker
  npm install @cdktf/provider-github
  npm install @cdktf/provider-null

  You can also build any module or provider locally. Learn more https://cdk.tf/modules-and-providers

========================================================================================================

[2025-09-16T10:16:50.631] [INFO] default - Checking whether pre-built provider exists for the following constraints:
  provider: aws
  version : latest
  language: typescript
  cdktf   : 0.21.0

Pre-built provider information not found
Error: Pre-built provider information not found
    at HXt (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:167:2716)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async MP (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:167:2207)
    at async UP (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:167:3042)
    at async YP (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:167:4088)
    at async VN.hasPrebuiltProvider (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:172:183)
    at async VN.addProvider (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:167:8837)
    at async Mse (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:173:2071)
    at async ojt (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:173:140)
    at async kze (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:513:2980)
Collecting Debug Information...
/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53
        throw ex;
        ^

Error: Pre-built provider information not found
    at HXt (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:167:2716)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async MP (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:167:2207)
    at async UP (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:167:3042)
    at async YP (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:167:4088)
    at async VN.hasPrebuiltProvider (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:172:183)
    at async VN.addProvider (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:167:8837)
    at async Mse (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:173:2071)
    at async ojt (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:173:140)
    at async kze (/Users/name/.nvm/versions/node/v20.12.2/lib/node_modules/cdktf-cli/bundle/bin/cmds/handlers.js:513:2980)

Node.js v20.12.2

Versions

language: typescript
cdktf-cli: 0.21.0
node: v20.12.2
cdktf: 0.21.0
constructs: 10.4.2
jsii: null
terraform: 1.9.8
arch: arm64
os: darwin 23.6.0
providers

Providers

cdktf provider list
┌┐
││
└┘
since it's cdktf init in an empty dir, there is no provider list.

Gist

No response

Possible Solutions

No response

Workarounds

No response

Anything Else?

No response

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

[elovelan]

$ curl -i https://www.cdk.tf/.well-known/prebuilt-providers.json
HTTP/2 404 
cache-control: public, max-age=0, must-revalidate
content-type: text/plain; charset=utf-8
date: Tue, 16 Sep 2025 17:42:33 GMT
server: Vercel
strict-transport-security: max-age=63072000
x-vercel-error: DEPLOYMENT_NOT_FOUND
x-vercel-id: iad1::8w4jl-1758044553310-928a40e46c15
content-length: 107

The deployment could not be found on Vercel.

DEPLOYMENT_NOT_FOUND

iad1::8w4jl-1758044553310-928a40e46c15

[elovelan]

not sure I'd recommend this, but manually changing the value in the source from https://www.cdk.tf/.well-known/prebuilt-providers.json to https://raw.githubusercontent.com/cdktf/cdktf-repository-manager/main/provider.json at least unblocks this issue.

[jwharris38]

I also was having trouble with this today and spent quite some time messing around, had you not posted this I probably would still be losing my mind. Here is something that might help though fwiw. I found running cdktf init with the provider explicitly added in the providers param allowed the cdktf init to generate files.

C:\Users\name\helpme\onemore> cdktf init --template=python --providers="aws@~>6.0" --local
Note: By supplying '--local' option you have chosen local storage mode for storing the state of your stack.
This means that your Terraform state file will be stored locally on disk in a file 'terraform.<STACK NAME>.tfstate' in the root of your project.
? Project Name onemore
? Project Description A simple getting started project for cdktf.
? Do you want to send crash reports to the CDKTF team? Refer to https://developer.hashicorp.com/terraform/cdktf/create-and-deploy/configuration-file#enable-crash-reporting-for-the-cli for more information no
Pipfile.lock not found, creating...
Locking  dependencies...
Locking  dependencies...
Installing cdktf~=0.21.0...
Installation Succeeded
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Upgrading cdktf~=0.21.0 in  dependencies.
Building requirements...
Resolving dependencies...
Success!
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
All dependencies are now up-to-date!
All dependencies are now up-to-date!
========================================================================================================

  Your cdktf Python project is ready!

  cat help                Prints this message

  Compile:
    pipenv run ./main.py  Compile and run the python code.

  Synthesize:
    cdktf synth [stack]   Synthesize Terraform resources to cdktf.out/

  Diff:
    cdktf diff [stack]    Perform a diff (terraform plan) for the given stack

  Deploy:
    cdktf deploy [stack]  Deploy the given stack

  Destroy:
    cdktf destroy [stack] Destroy the given stack

  Learn more about using modules and providers https://cdk.tf/modules-and-providers

Use Providers:

  You can add prebuilt providers (if available) or locally generated ones using the add command:

  cdktf provider add "aws@~>3.0" null kreuzwerker/docker

  You can find all prebuilt providers on PyPI: https://pypi.org/user/cdktf-team/
  You can also install these providers directly through pipenv:

  pipenv install cdktf-cdktf-provider-aws
  pipenv install cdktf-cdktf-provider-google
  pipenv install cdktf-cdktf-provider-azurerm
  pipenv install cdktf-cdktf-provider-docker
  pipenv install cdktf-cdktf-provider-github
  pipenv install cdktf-cdktf-provider-null

  You can also build any module or provider locally. Learn more: https://cdk.tf/modules-and-providers

========================================================================================================
[2025-09-16T22:33:13.231] [INFO] default - Checking whether pre-built provider exists for the following constraints:
  provider: aws
  version : ~>6.0
  language: python
  cdktf   : 0.21.0

Pre-built provider information not found
Error: Pre-built provider information not found
    at HXt (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:167:2716)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async MP (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:167:2207)
    at async UP (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:167:3042)
    at async YP (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:167:4088)
    at async VN.hasPrebuiltProvider (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:172:183)
    at async VN.addProvider (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:167:8837)
    at async Mse (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:173:2071)
    at async ojt (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:173:140)
    at async kze (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:513:2980)
Collecting Debug Information...
C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\node_modules\yoga-layout-prebuilt\yoga-layout\build\Release\nbind.js:53
        throw ex;
        ^

Error: Pre-built provider information not found
    at HXt (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:167:2716)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async MP (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:167:2207)
    at async UP (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:167:3042)
    at async YP (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:167:4088)
    at async VN.hasPrebuiltProvider (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:172:183)
    at async VN.addProvider (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:167:8837)
    at async Mse (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:173:2071)
    at async ojt (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:173:140)
    at async kze (C:\Users\name\Local\nvm\v20.17.0\node_modules\cdktf-cli\bundle\bin\cmds\handlers.js:513:298
Node.js v20.17.0

After running cdktf init and explicitly defining the provider I still get the error, but our files are generated. However, this will still not have the provider included see below:

PS C:\Users\name\helpme\onemore> cdktf get
[2025-09-16T22:33:47.005] [WARN] default - WARNING: No providers or modules found in "cdktf.json" config file, therefore cdktf get does nothing.

This isn't the most optimal, but you can manually add the provider package and necessary modules now that your cdktf.json file is initialized in the directory:

Now run cdktf get:

PS C:\Users\name\helpme\onemore> cdktf get
Generated python constructs in the output directory: imports

Successfully runs and adds the provider package to the imports directory as defined by cdktf.json:

Then I run cdktf synth and cdktf diff successfully:

PS C:\Users\name\helpme\onemore> cdktf get
Generated python constructs in the output directory: imports
PS C:\Users\name\helpme\onemore> cdktf synth

Generated Terraform code for the stacks: onemore
PS C:\Users\name\helpme\onemore> cdktf diff
onemore
onemore  
Initializing the backend...
         
onemore
         Successfully configured the backend "local"! Terraform will automatically
         use this backend unless the backend configuration changes.
         Initializing provider plugins...
Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
         any changes that are required for your infrastructure. All Terraform commands
         should now work.

If you ever set or change modules or backend configuration for Terraform,
         rerun this command to reinitialize your working directory. If you forget, other
         commands will detect it and remind you to do so if necessary.

onemore  Success! Terraform has validated the lock file and found no need for changes.
onemore  No changes. Your infrastructure matches the configuration.


onemore  Terraform has compared your real infrastructure against your configuration
         and found no differences, so no changes are needed.

Again, not the best workaround but you are able to continue moving along with your project at least.

Versions

language: python
cdktf-cli: 0.21.0
node: v20.17.0
cdktf: 0.21.0
constructs: 10.4.2
jsii: 1.114.1
terraform: 1.13.2
arch: x64
os: win32 10.0.26100
python: Python 3.11.9
pip: pip 25.2
pipenv: pipenv, version 2025.0.4
providers
aws@~>6.0 (LOCAL)
terraform provider version: 6.13.0

[EmekaNnaji]

I'm also getting this issue while attempting to install the latest version of cdktf-cli:

 npm install -g cdktf-cli@latest 

[HackedRico]

Hello,

I was experiencing this issue too, however was able to find a solution. It seems like the cdktf init command's --providers field is looking for an array by default as shown in the help menu.

Thus I tried doing cdktf init --template=python --providers=aws --local and it worked!

Here are the logs in which CDKTF does find the AWS Pre-built Provider and installs it.

Note: By supplying '--local' option you have chosen local storage mode for storing the state of your stack.
This means that your Terraform state file will be stored locally on disk in a file 'terraform.<STACK NAME>.tfstate' in the root of your project.
? Project Name test
? Project Description A simple getting started project for cdktf.
? Do you want to send crash reports to the CDKTF team? Refer to 
https://developer.hashicorp.com/terraform/cdktf/create-and-deploy/configuration-file#enable-crash-reporting-for-the-cli for more 
information no
Creating a virtualenv for this project
Pipfile: /Users/johndoe/Documents/GitHub/CDKTF-Convert/test/Pipfile
Using /usr/local/bin/python33.13.7 to create virtualenv...
⠋ Creating virtual environment...created virtual environment CPython3.13.7.final.0-64 in 615ms
  creator CPython3macOsBrew(dest=/Users/johndoe/.local/share/virtualenvs/test-WGJoxhNf, clear=False, no_vcs_ignore=False, 
global=False)
  seeder FromAppData(download=False, pip=bundle, via=copy, app_data_dir=/Users/johndoe/Library/Application Support/virtualenv)
    added seed packages: pip==25.2
  activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator

✔ Successfully created virtual environment!
Virtualenv location: /Users/johndoe/.local/share/virtualenvs/test-WGJoxhNf
Pipfile.lock not found, creating...
Locking  dependencies...
Locking  dependencies...
Updated Pipfile.lock (4e61a4ba9e6f02f50f68627253af5ababd9b1b4c1e10294e48158e1f42c0c5a6)!
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Installing dependencies from Pipfile.lock (c0c5a6)...
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Installing cdktf~=0.21.0...
✔ Installation Succeeded
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Installing dependencies from Pipfile.lock (c0c5a6)...
All dependencies are now up-to-date!
Upgrading cdktf~=0.21.0 in  dependencies.
Building requirements...
Resolving dependencies...
✔ Success!
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Installing dependencies from Pipfile.lock (dd9f43)...
All dependencies are now up-to-date!
Installing dependencies from Pipfile.lock (dd9f43)...
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Installing pytest...
✔ Installation Succeeded
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Installing dependencies from Pipfile.lock (dd9f43)...
All dependencies are now up-to-date!
Upgrading pytest in  dependencies.
Building requirements...
Resolving dependencies...
✔ Success!
Building requirements...
Resolving dependencies...
✔ Success!
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Installing dependencies from Pipfile.lock (e244ae)...
All dependencies are now up-to-date!
Installing dependencies from Pipfile.lock (e244ae)...
========================================================================================================

  Your cdktf Python project is ready!

  cat help                Prints this message

  Compile:
    pipenv run ./main.py  Compile and run the python code.

  Synthesize:
    cdktf synth [stack]   Synthesize Terraform resources to cdktf.out/

  Diff:
    cdktf diff [stack]    Perform a diff (terraform plan) for the given stack

  Deploy:
    cdktf deploy [stack]  Deploy the given stack

  Destroy:
    cdktf destroy [stack] Destroy the given stack

  Learn more about using modules and providers https://cdk.tf/modules-and-providers

Use Providers:

  You can add prebuilt providers (if available) or locally generated ones using the add command:
  
  cdktf provider add "aws@~>3.0" null kreuzwerker/docker

  You can find all prebuilt providers on PyPI: https://pypi.org/user/cdktf-team/
  You can also install these providers directly through pipenv:

  pipenv install cdktf-cdktf-provider-aws
  pipenv install cdktf-cdktf-provider-google
  pipenv install cdktf-cdktf-provider-azurerm
  pipenv install cdktf-cdktf-provider-docker
  pipenv install cdktf-cdktf-provider-github
  pipenv install cdktf-cdktf-provider-null

  You can also build any module or provider locally. Learn more: https://cdk.tf/modules-and-providers

========================================================================================================
[2025-09-19T14:27:27.476] [INFO] default - Checking whether pre-built provider exists for the following constraints:
  provider: aws
  version : latest
  language: python
  cdktf   : 0.21.0

[2025-09-19T14:27:29.672] [INFO] default - Found pre-built provider.
Installing package cdktf-cdktf-provider-aws @ 21.11.0 using pipenv.
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Installing cdktf-cdktf-provider-aws~=21.11.0...
✔ Installation Succeeded
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Installing dependencies from Pipfile.lock (e244ae)...
All dependencies are now up-to-date!
Upgrading cdktf-cdktf-provider-aws~=21.11.0 in  dependencies.
Building requirements...
Resolving dependencies...
✔ Success!
Building requirements...
Resolving dependencies...
✔ Success!
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Installing dependencies from Pipfile.lock (a7a66a)...
All dependencies are now up-to-date!
Installing dependencies from Pipfile.lock (a7a66a)...
Package installed.

[hinling-blisspoint]

Looks like the option --local works as a workaround for now. Thanks everyone for the tip! I ended up still just running the cdktf init --template="typescript" --providers="aws" command and it created template files. (just cdkt init does nothing and that's what I used at the very beginning). I do use terraform cloud but that can be done later when doing cdktf diff or cdktf list