## TL;DR
Install the provider package directly: `pipenv install cdktf-cdktf-provider-aws` (or `pip install cdktf-cdktf-provider-aws==[version]`), instead of going through `cdktf provider add` for that version.

## The error
Running `cdktf provider add "aws@~>4.0"` fails because pip reports no matching distribution for the resolved version (e.g. v9.0.36).

## Fix it
1. Skip `cdktf provider add` for this provider.
2. Install the pre-built Python provider package directly: `pipenv install cdktf-cdktf-provider-aws` or pin it: `pip install "cdktf-cdktf-provider-aws==[version]"`.
3. Run `cdktf synth` and confirm the AWS constructs resolve.

Expected result: synth succeeds with the AWS provider available.

## When to use this
- `cdktf provider add "aws@~>4.0"` (or similar) fails with "no matching distribution found"
- You use Python and want the pre-built provider

## When NOT to use this
- The failure is a network/proxy error rather than version resolution
- You use TypeScript (use npm and @cdktf/provider-aws)

## Root cause
`cdktf provider add` resolves a provider version and then shells out to the language package manager; when the resolved version has no published artifact for that language (a release-skew window), the install fails. Installing the package directly lets you pick a version that actually exists on PyPI.

## Edge cases
- Pin the version in your Pipfile/requirements so CI does not re-resolve to the missing one.