HashiCorp archived CDK for Terraform on December 10, 2025. Existing stacks still deploy, but nothing will be fixed. Export to HCL, move to Pulumi, move to AWS CDK, or adopt the community fork: the effort and risk of each.
CDK for Terraform let teams write Terraform in TypeScript, Python or Go. HashiCorp archived the repository on December 10, 2025, saying it had not found product-market fit at scale. The code is read-only. Your stacks still synthesize and deploy, but there will be no bug fixes, no security fixes and no support for new Terraform features.
Nothing breaks today. The risk grows over time: a Node.js upgrade, a provider release or a Terraform change that the archived tool cannot follow. Plan the move this year, while you choose the timing.
Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
If the CDKTF code is mostly flat resource declarations, export to HCL. You were using a language for little benefit, and HCL with modules is a fine destination. This is the fastest way off.
If the code has real abstractions, such as loops over accounts, generated resources or shared libraries, Pulumi preserves them. Budget time for state import and a plan that shows no replacements.
If everything is on AWS and the team already knows CDK, AWS CDK is the cleanest long-term result and the most work. CloudFormation resource import works per resource type, and not every type supports it.
The fork buys time. Use it if a migration this year is not possible, and decide in advance how long you will stay.
Pin the CDKTF, provider and Terraform versions you run today, so nothing changes under you during the migration.
Back up state before touching it.
Migrate one stack at a time, starting with the least critical, and require a plan with zero replacements before applying.
Delete the old code paths once a stack has moved, so there is one source of truth.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
Pulumi vs Terraform in 2026: Why We Pick Pulumi When It Isn't Only AWS (and CDK When It Is)
Our rule is short: CDK when everything is on AWS, Pulumi over Terraform when it isn't. Pulumi gives you real languages, real tests and an engine you can call from code, and it can use any Terraform or OpenTofu provider, so the ecosystem comes with it. What Pulumi costs, where Terraform is still the better call, and how to move.
Read
CDK vs Terraform vs OpenTofu vs Pulumi in 2026: Choosing Infrastructure as Code
Terraform is IBM's now, OpenTofu has shipped features Terraform does not have, CDK for Terraform is archived, HCP Terraform's free tier is capped at 500 resources, and AWS CDK gained Mixins. What changed, what each tool costs, and how we choose.
Read
As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.