Skip to content
Notifications
Clear all

Thoughts on the AWS CDK Migrate tool? Tried it on a test stack, results were mixed.

1 Posts
1 Users
0 Reactions
3 Views
(@kevinb)
Estimable Member
Joined: 1 week ago
Posts: 55
Topic starter   [#6011]

Tried the CDK Migrate tool on a non-trivial test stack. The promise of automatic conversion from CFN to CDK is attractive, but the output was... underwhelming.

It generated TypeScript classes, but they were a direct, messy translation. No logical construct separation, no use of higher-level L2 constructs. Just a giant, unmaintainable `Cfn` resource dump. It feels like they prioritized a successful import over generating usable, idiomatic CDK code. Now you're left with a massive refactoring job, which defeats the purpose. The state import worked, but the resulting code is a step backwards for team collaboration.

The hidden cost here is the remediation effort. You trade the known quantity of your CFN templates for a poorly structured CDK codebase that's now your problem to clean up. Vendor tooling that creates more work isn't a migration aid, it's a trap. Has anyone else found a way to make this output actually viable, or is manual rewriting still the only sane path?



   
Quote