{"name":"cdkd: Deploy AWS CDK Apps Faster with Direct AWS SDK Calls","description":"cdkd is a drop-in CLI for AWS CDK apps, using direct AWS SDK calls instead of CloudFormation for faster dev and test deployments. It complements the AWS CDK CLI, with the project advising against production use for now.","github":"https://github.com/go-to-k/cdkd","url":"https://osrepos.com/repo/go-to-k-cdkd","source":"osrepos.com","sourceDescription":"This repository profile is provided by osrepos.com, an open source repository discovery platform.","repositoryProfile":"https://osrepos.com/repo/go-to-k-cdkd","generatedFor":"open source discovery and AI-assisted research","markdown":"https://osrepos.com/repo/go-to-k-cdkd.md","json":"https://osrepos.com/repo/go-to-k-cdkd.json","topics":["typescript","cli","developer-tools","aws-cdk","cloudformation","infrastructure-deployment"],"keywords":["typescript","cli","developer-tools","aws-cdk","cloudformation","infrastructure-deployment"],"stars":null,"summary":"cdkd is a drop-in CLI for AWS CDK apps, using direct AWS SDK calls instead of CloudFormation for faster dev and test deployments. It complements the AWS CDK CLI, with the project advising against production use for now.","content":"## Overview\n\ncdkd (CDK Direct) is a TypeScript CLI for existing AWS CDK apps. It uses direct AWS SDK calls rather than CloudFormation to deploy resources, aiming to shorten the development and testing feedback loop without requiring changes to CDK app code.\n\nThe project positions itself as a companion to the AWS CDK CLI, not a production replacement. Teams can use `cdkd` for rapid iteration and retain the standard CLI for production workflows that need full CloudFormation tooling. It also provides local execution against deployed stacks and import/export paths between cdkd and CloudFormation.\n\n## Key Features\n\n- Deploy and destroy existing CDK apps through the `cdkd` CLI.\n- Use `--no-wait` to skip resource stabilization waits for faster iteration.\n- Run `list` and `diff` to inspect stacks and proposed changes.\n- Run functions, APIs, and ECS tasks locally with references to a deployed stack's environment variables, secrets, and resources.\n- Import existing stacks into cdkd or export them back to CloudFormation.\n- Includes a skill for AI coding agents to guide cdkd usage.\n\n## Use Cases\n\n- CDK developers iterating on dev or test stacks who want shorter deploy and teardown cycles.\n- Teams building with AI coding agents that need repeated infrastructure spin-up and tear-down during development.\n- Developers testing functions, APIs, or ECS tasks locally while resolving configuration and resources from a real deployed stack.\n- Teams evaluating a faster deployment path for existing CDK apps while keeping the AWS CDK CLI for production.\n\n## Our Take\n\ncdkd is an actively maintained, clearly scoped accelerator for CDK development, but its own guidance limits it to dev and test rather than production.\n\n**Good fit if:**\n- Your team already has AWS CDK apps and wants to try direct-SDK deploys without migrating app code.\n- Short deploy and destroy cycles matter for development or AI-agent-driven iteration.\n- You can run Node.js 22.12 or later and keep production deployments on the AWS CDK CLI.\n\n**Look elsewhere if:**\n- You need a production-ready replacement for the AWS CDK CLI or rely on full CloudFormation tooling in every environment.\n- You cannot meet the Node.js 22.12 minimum runtime requirement.\n- Your workflow depends on CloudFormation behavior that cdkd's direct AWS SDK approach does not provide.\n\n## Project Health\n\n| Signal | Value |\n|---|---|\n| Status | **Active**: regular commits and releases |\n| Last commit | 2026-10-30 (today) |\n| Commits, last 90 days | 100+ |\n| Releases, last 12 months | 100+ (latest v0.311.0, 2026-10-30) |\n| Contributors | 12 (top contributor: 70% of commits) |\n| Issues closed, last 90 days | 27+ (typically closed in 0 days) |\n| Pull requests merged, last 90 days | 98 (typically merged in 0 days) |\n| Project age | 7 months |\n\nChecked on 2026-10-30 with the GitHub API.\n\n## Project Facts\n\n- Language: TypeScript\n- License: Apache-2.0\n- Stars: 156\n- Forks: 12\n- Topics: aws, aws-cdk, aws-cloudformation, aws-sdk, awscdk, cdk, cloudformation\n- Archived: no\n\n## What You Need\n\nDetected in the repository:\n\n- Node.js >=22.12.0 (from package.json)\n- A test suite and automated checks on GitHub Actions\n\n## Getting Started\n\nInstall the CLI with npm:\n\n```bash\nnpm i -g @go-to-k/cdkd\n```\n\nRun `cdkd bootstrap` once per AWS account, then use `cdkd deploy` in a CDK app. See the [README](https://github.com/go-to-k/cdkd) and [documentation](https://cdkd.dev) for setup and command details.\n\n## License in Plain Words\n\n**Apache-2.0** (permissive).\n\n- Commercial use: yes\n- Modify and redistribute: yes\n- You must keep: the license, the NOTICE file and a note of your changes\n- Share your changes: no\n- Includes an explicit patent grant from the contributors\n\nA summary, not legal advice: the LICENSE file is what applies.\n\n## Considerations\n\n- The project explicitly describes itself as not yet production-ready and recommends it for dev/test workflows.\n- The CLI requires Node.js 22.12 or later.\n- Direct SDK deployment differs from CloudFormation-based deployment. Validate behavior against your app and AWS resources before adopting it in development workflows.\n- The repository is actively maintained, with recent commits and releases and ongoing issue and pull-request activity. Its measured contributor base is not concentrated in a single contributor.","metrics":{"detailViews":4,"githubClicks":0},"dates":{"published":null,"modified":"2026-10-30T13:37:27.000Z"}}