TL;DR
When you use AWS Emulator for development with AWS CDK, combining it with cdkd gives you the following benefits:
cdkd automatically configures the connection to AWS Emulator, and environment variables for Lambda and other resources are resolved automatically from your CDK code, so you don't need a .env file
You can freely switch the connection target per service, for example using real AWS for secrets and reference data/files while having the app write to AWS Emulator (no need to recreate real AWS data locally)
Application code such as Lambda functions runs directly from source without being deployed to AWS Emulator, so you can try out changes right away without redeploying
AWS Emulator and cdkd (CDK Direct)
AWS Emulator is a tool released in November 2026 that emulates AWS APIs locally.…