AWS SDK instead of CloudFormation ‣ Fully drop-in CDK compatible - Your existing CDK app code runs as-is. - Just replace cdk deploy with cdkd deploy. ‣ Up to 15x faster deploys - Direct SDK calls, aggressive parallelization, and --no-wait to skip slow stabilization waits - Faster than Terraform and CloudFormation Express mode https://github.com/go-to-k/cdkd
than replacing it ‣ Use cdkd in dev/test for rapid iteration (with zero code changes) ‣ Use CDK CLI in stg/prod for full CloudFormation tooling (as usual) • Disposable and prototype environments in AI-driven development ‣ cdkd destroys super fast too • Ephemeral environments triggered by Pull Requests ‣ Dramatically reduces CI build times
‣ Just run ̀cdkl <command> (e.g. start-api)̀ in your CDK project directory - ̀sam local̀ for CDK ‣ Related resource information can also be automatically retrieved from the AWS environment. - Run locally: Application code (e.g. Lambda) - Connect to real AWS resources: Secret / S3 / DB / etc. ‣ → No hand-written .env les, no hand-seeded test data fi https://github.com/go-to-k/cdk-local
even on unde ned properties in CDK (CloudFormation) - Catches drift that ̀cdk drift̀ misses ‣ Can record, revert, or ignore fi https://github.com/go-to-k/cdk-real-drift
CDK stack ‣ CloudFront: ap-northeast-1, ACM: us-east-1 ‣ 1 stack in CDK code → 1 CloudFormation stack per region at synth time fi https://github.com/go-to-k/cdk-multi-region-stack
delete the entire stack with no orphaned resources - Including resources that fail with CFn deletion (or FORCE̲DELETE̲STACK) ‣ No custom recourses like the autoDeleteObjects for S3 https://github.com/go-to-k/delstack