AWS Cloud Development Kit (AWS CDK) Reviews & Product Details

What I like most about AWS CDK is that it lets me define cloud infrastructure using familiar programming languages like TypeScript and Python, rather than having to write complex YAML or JSON templates. This makes infrastructure as code much easier for me to manage, reuse, and maintain over time. I also appreciate the reusable constructs, the built-in AWS integration, and the ability to deploy and manage resources efficiently. Review collected by and hosted on G2.com.

There’s a steep learning curve, especially for beginners. Debugging deployment errors can be challenging at times, and understanding the generated CloudFormation templates isn’t always straightforward. Review collected by and hosted on G2.com.

What I like most about AWS CDK is that it lets developers define cloud infrastructure using familiar programming languages like Python, TypeScript, Java, and C#, rather than manually writing large CloudFormation templates. As a result, infrastructure development feels more maintainable and reusable, and it’s also easier to keep it aligned with application code.

I also appreciate the ability to create reusable constructs and apply standard software engineering practices—such as version control, testing, and code reviews—which can make day-to-day infrastructure management much smoother. Review collected by and hosted on G2.com.

AWS CDK introduces an abstraction layer over CloudFormation, so troubleshooting deployment issues sometimes requires understanding both CDK and the underlying CloudFormation resources. Upgrading between CDK versions can also occasionally require code changes. Review collected by and hosted on G2.com.

What I like best about AWS CDK is the ability to define cloud infrastructure using real programming languages like TypeScript, Python, and Java instead of writing lengthy YAML or JSON templates. This means I can use familiar concepts like loops, conditionals, functions, and classes to build infrastructure, which dramatically reduces boilerplate and makes complex setups much easier to manage. Review collected by and hosted on G2.com.

Deployment speed is a pain point. Because CDK ultimately runs CloudFormation under the hood, deployments can be slow, sometimes taking 10 to 20 minutes or more for larger stacks. Failed deployments often trigger lengthy rollbacks, which interrupts the development feedback loop and makes iterating on infrastructure frustrating compared to tools that apply changes more directly. Review collected by and hosted on G2.com.

I like its testing capabilities as it enables unit testing of infrastructure logic prior to deployment. Review collected by and hosted on G2.com.

I dislike its learning curve because it requires understanding both standard software development patterns and AWS cloud primitives. Review collected by and hosted on G2.com.

I just like how easy it is to use, honestly. It's pretty easy to set up. I also value the L2 constructs in CDK. They are beneficial when I need more secure cloud storage or when setting up written standard configurations, requiring manually defined encryption, access blocks, and public restriction tools. Review collected by and hosted on G2.com.

I would say the local mocking is a limitation. When testing my infrastructure locally on my computer before deploying it to the cloud, it's pretty slow. Review collected by and hosted on G2.com.

I find the AWS Cloud Development Kit (AWS CDK) incredibly easy for deploying applications using AWS services. The ability to use programming languages like TypeScript, which our codebase already utilizes, is fantastic because it means I can work in a familiar language that enhances my comfort level with coding for CDK. The process of building DevOps architectures with line coding languages is streamlined, allowing me to reuse and deploy easily across various environments. Setting up and developing our CI/CD pipelines has also become effortless. I love that CDK enables the creation of custom constructs, providing a high level of abstraction in coding. Another standout feature for me is observing changes in cloud formations via CDK, ensuring I am always aware of what changes are being applied. The reusability of code across projects maintains consistency within our organization, which is highly beneficial. Review collected by and hosted on G2.com.

I find that if my infrastructure team is more comfortable with YAML and Terraform, adapting to AWS CDK's use of TypeScript and Python can be challenging for them. When we're working extensively in Terraform, it becomes slightly difficult to integrate with AWS CDK. Additionally, the abstraction provided by CDK sometimes leads to issues, such as leaks that make debugging complex and not straightforward. I feel AWS CDK is more suited for smaller projects; as projects grow larger, understanding the infrastructure code becomes complicated, presenting a notable learning curve and complicating architectural decision-making. Review collected by and hosted on G2.com.

Being able to define infrastructure as code in a deterministic manner provides a better overall DX, given changes are easily reviewable and reversible. Review collected by and hosted on G2.com.

Sometimes it lags behind existing features or doesn't provide the full set of options. Review collected by and hosted on G2.com.

AWS CDK assists us to organize cloud resources in an orderly manner through code. It simplifies deployments and makes them more reliable and also easier. Review collected by and hosted on G2.com.

I sometimes find it difficult to debug problems because sometimes errors are not very obvious and can involve checking in several settings. Review collected by and hosted on G2.com.

The best thing i like about AWS CDK is that it's let's me define cloud infrastructure using familiar programming language. Review collected by and hosted on G2.com.

One thing i dislike about learning curve can be steep for beginners. Review collected by and hosted on G2.com.

AWS CDK allows defining the infrastructure of Indoff University using real code in TypeScript, making the deployment process reproducible and easy to version alongside the rest of the project on GitHub. Review collected by and hosted on G2.com.

The documentation can be confusing for specific use cases, and the synthesis time of stacks in large projects can become slow. Additionally, deployment errors are sometimes not very descriptive. Review collected by and hosted on G2.com.