CloudFormation to Terraform Migration

Point this agent at your CloudFormation templates and ask it to plan the move to Terraform. The whole workflow is built around one invariant: the migration is import-first, so terraform plan shows zero resource churn — no create, no replace, no destroy — before you retire a stack.

What it does

1. Map your stacks: resources, parameters, conditions, intrinsics (Ref / GetAtt / Sub / FindInMap), nested stacks, custom resources, and drift status
2. Plan a dependency-ordered, import-first migration with state layout and backend decisions per stack
3. Generate HCL plus import blocks — conditions→count/for_each, Mappings→locals, Outputs/exports→outputs + remote state, module boundaries per nested stack
4. Sandbox — run terraform init + plan against the sandbox account and report PASS/PARTIAL/FAIL by reading the plan for churn

Prerequisites

• AWS_ACCESS_KEY_ID — sandbox account credentials with least-privilege read and targeted import permissions
• AWS_SECRET_ACCESS_KEY — paired secret key
• AWS_REGION — region of the sandbox stacks
• TF_CLOUD_TOKEN — optional; HCP Terraform token when plans should run in a remote workspace

Current scope

This solution translates templates and imports live resources into Terraform state. It does not rewrite Lambda-backed custom resources (it flags them with a redesign sketch), does not translate SAM or macro-transformed templates before they are expanded, does not manage StackSets, and never deletes a CloudFormation stack — retiring stacks stays a human decision after plans are clean.