AWS Cloud Development Kit (CDK) Reviews

AWS Cloud Development Kit (CDK) is an open-source software used to model and provision cloud applications and resources with familiar programming languages. It supports various languages like JavaScript, Python, Java, C#, and Go. The benefit is to improve the experience of working with infrastructure as code by providing higher level and reusable constructs that enable developers to create and manage AWS resources more efficiently and with less boilerplate code compared to traditional configuration files like AWS CloudFormation templates.

Earlier I was using AWS CloudFormation templates. When I switched to AWS Cloud Development Kit (CDK), I was able to reuse the constructs that enable me to create and manage AWS resources more efficiently, and it has less boilerplate code compared to the traditional configuration files like CloudFormation templates. It supports all the languages, including TypeScript, JavaScript, Python, Java, C#, and Go, which made my work easy.

Stacks contain definitions for one or more cloud resources in AWS. Stacks are also called the unit of deployments. Any number of stacks can be defined in an application in CDK.

The best features that AWS Cloud Development Kit (CDK) offers include providing a better experience of working with infrastructure as code by offering higher level and usable constructs, choosing my preferred language, allowing the use of any programming elements like parameters, conditions, conditionals, loops, compositions, and inheritance to define the desired outcome of infrastructure. There is also the CDK library of infrastructure constructs. AWS Cloud Development Kit (CDK) integrates with CloudFormation to deploy and provision infrastructure on AWS, which are some of the benefits and features.

The ability to choose my preferred programming language has helped my workflow significantly, as I can use my preferred languages such as JavaScript or C#, along with the programming elements in that language such as parameters, conditionals, loops, compositions, and inheritance to define the desired outcome of my infrastructure and application logic. I benefit from developing infrastructure in my preferred IDE, which includes syntax highlighting and intelligent code completion that has helped my workflow.

The benefits of AWS Cloud Development Kit (CDK) include multi-language support, so if I am familiar with a specific programming language, instead of writing YAML or JSON files, I can use my own language such as TypeScript, JavaScript, Python, Java, C#, .NET, or Go. There is also IDE support and improved developer experience, along with reusable components, namely AWS Cloud Development Kit (CDK) constructs that encapsulate AWS best practices. These have positively impacted my organization.

Reduced errors and an improvement in the code are specific outcomes I can share regarding AWS Cloud Development Kit (CDK). Earlier, I used to write JSON or YAML syntax. After the introduction of typed languages like TypeScript, I can catch configuration errors at compile time rather than during deployment, which significantly reduces debugging time. This has greatly reduced the errors I encounter.

AWS Cloud Development Kit (CDK) can be improved with the implementation of best practices for the constructs, such as using L2 and L3 constructs when available. They could include sensible defaults and best practices, and also improve organizing the code. Adding unit tests for constructs would be beneficial, along with enhancing security. Optimizing the development and deployment pipeline, improving configuration management, performance, and the documentation part with clearer comments explaining certain configurations would make it better.

I have been using AWS Cloud Development Kit (CDK) for the past three years.

AWS Cloud Development Kit (CDK) is quite stable in my experience.

AWS Cloud Development Kit (CDK) scalability is quite good. It delivers excellent performance, especially with support for multiple languages, which makes it very scalable. AWS Cloud Development Kit (CDK) simplifies defining auto scaling configurations using familiar programming constructs. It allows the setup of EC2 auto scaling groups, ECS service scaling, Lambda concurrency, and DynamoDB capacity with just a few lines of code, and it also has reusable patterns for scaling and a multi-stack architecture.

I have interacted with customer support for AWS Cloud Development Kit (CDK), and the support has been excellent.

Positive

The solution I was using before switching to AWS Cloud Development Kit (CDK) was AWS CloudFormation, which uses YAML and JSON templates. It is a native AWS service that AWS Cloud Development Kit (CDK) compiles down to. CloudFormation had no additional tooling required beyond AWS, with direct integration with AWS services.

The pricing, setup cost, and licensing have been quite decent. Regarding AWS Cloud Development Kit (CDK), the pricing comes at no extra cost. AWS Cloud Development Kit (CDK) itself is free, making it one of the best things about it. I only pay for the resources that AWS Cloud Development Kit (CDK) provisions, which include compute resources, storage, networking, and other services. This cost is much less compared to traditional hardware solutions.

Before choosing AWS Cloud Development Kit (CDK), I evaluated AWS CloudFormation, which has the native integration with AWS, directly compiles down to YAML or JSON templates, requires no additional tooling, and is best for teams comfortable with declarative templates.

AWS Cloud Development Kit (CDK) has a lot to offer. I chose a rating of 10 because of the benefits it provides, such as using familiar programming languages. I can use most of the languages that are covered: TypeScript, JavaScript, Python, Java, C#, .NET, or Go. It provides support for IDE and an excellent developer experience, including syntax highlighting, intelligent code completion, inline documentation, refactoring tools, and debugging capabilities. It has reusable components, higher-level abstractions, type safety, and error checking because of the TypeScript language used. It integrates application and infrastructure code, allowing for predictable and repeatable deployments, automatic rollback on errors, drift detection, change sets for reviewing changes before deployment, testing the infrastructure, and simplified multi-environment management.

I would advise others looking into AWS Cloud Development Kit (CDK) that they should definitely start using it now because if someone is using AWS CloudFormation, this is a significant upgrade with scalability, reusable patterns, multi-stack architecture, multiple language support, and integration with AWS scaling services. AWS Cloud Development Kit (CDK) is quite beneficial for larger teams and projects, making a significant impact. Most of the features and benefits of AWS Cloud Development Kit (CDK) that I have mentioned include significant advantages over scalability, multi-language support, and cost-effectiveness. I essentially pay nothing for AWS Cloud Development Kit (CDK), only for whatever I use, and it helps organize my code better while implementing best practices for constructs.

I rate AWS Cloud Development Kit (CDK) a 10 out of 10 based on all these factors.

My main use case for AWS Cloud Development Kit (CDK) is to communicate with AWS services rather than using it from the CLI or from the console. For example, if we have a service called S3 and our website or web app application needs some global storage, we can call the S3 bucket via AWS Cloud Development Kit (CDK). For the Python language, we can use the Boto3 library to call the AWS service.

With AWS Cloud Development Kit (CDK), I use AWS Secrets Manager, which is one of the services, to fetch the environment variables. I am also using AWS Cloud Development Kit (CDK) for storage purposes, and there are other services such as AWS Textract, AWS Bedrock, and AWS Polly that I am utilizing. All these services are for the developer, and AWS Cloud Development Kit (CDK) is mainly used for the development environment for developers to use those SaaS services and integrate them into our application. There are almost 256 plus services which we can call via AWS Cloud Development Kit (CDK).

The best feature of AWS Cloud Development Kit (CDK), in my opinion, is that AWS has its own SaaS services, and via AWS Cloud Development Kit (CDK), we can directly call them rather than creating them. Textract is one of the services; by code, it would take a lot of time to create that particular Textract service, calling OCRs and creating a bunch of code. Instead, by using AWS Cloud Development Kit (CDK), we can directly call that Textract service, give it the input, and it will give the output. We do not need to worry about the code that we are using; we are just using that SaaS via AWS Cloud Development Kit (CDK) and performing the operations. We just need to give the input and we will get the output.

AWS Cloud Development Kit (CDK) is easy to use, easy to manage, and easy to add or integrate into our existing workflow. There are a ton of services that are provided by AWS, so we can use those SaaS services directly rather than creating a bunch of code.

AWS Cloud Development Kit (CDK) has impacted my organization positively in terms of productivity. You do not need to write the code again and again; we can use SaaS services. The accuracy provided by AWS and AWS Cloud Development Kit (CDK) is much higher, so we do not need to worry about failures. All those things are managed by AWS. That is why it is easy to use and integrate.

To call AWS Cloud Development Kit (CDK), we just need to provide the credentials, which is important; without that, it will not be able to call. If that particular thing is on UAT or production, it is easy, as we can provide that particular role to that EC2 machine, and then it will call. Rather than providing the .env files and all, we can call that. However, when we are developing these particular things on the local machine, we just need to provide the .env files, so we do not have any other option. In that condition, if a developer accidentally pushes those environment variables to other things such as GitHub or any SCM, there are chances that a particular hacker or an unintended person can access our whole infrastructure. AWS could provide something where these are the keys which you can use in development mode. For production and UAT environments, you can provide the role. For those particular development keys, they would not have that much access, but we currently have to do this on our own while creating all these things.

That particular pain point regarding AWS Cloud Development Kit (CDK) is the only one I have; all other things are features.

I have been using AWS Cloud Development Kit (CDK) for almost 1.5 years with the Python language to communicate with the AWS cloud.

AWS Cloud Development Kit (CDK) is stable, based on the conditions.

I have not yet experienced any issues with the scalability of AWS Cloud Development Kit (CDK); it scales up or down without problems.

The customer support for AWS Cloud Development Kit (CDK) is good; based on the type of plan we have, it gives a good response, and all the things are understood.

Before using AWS Cloud Development Kit (CDK), I had experience with the particular Textract service which was taking time to create and the accuracy was low, which is why I switched to AWS Textract instead of writing the code.

You will find the product easy to use, easy to manage, and easy to add or integrate into your existing workflow.

My team saves significant time since adopting AWS Cloud Development Kit (CDK); if I had to create one Textract service from scratch, it would take almost a week, and four to five developers would work on that, testing and developing it from UAT to production. Instead of doing that, with AWS Cloud Development Kit (CDK), it takes almost a day or two, and the work of one or two developers to integrate that particular service.

The setup cost for AWS Cloud Development Kit (CDK) is based on how you are going to use things; it varies based on the conditions.

I did not evaluate other options before choosing AWS Cloud Development Kit (CDK); I went directly with AWS as I was experienced with it.

My advice for others looking into using AWS Cloud Development Kit (CDK) is that you can go for AWS Cloud Development Kit (CDK); it is easy to use, and we can integrate it into our development environment. Rather than writing code, we can use the ready-to-use SaaS products, and we can integrate those. The security that is provided is high, so you can go with AWS Cloud Development Kit (CDK); it is a good option. I found this interview good, and I believe you just need to update the knowledge base. The question asked about where I bought AWS Cloud Development Kit (CDK) from the marketplace is not the right question; AWS Cloud Development Kit (CDK) is not provided by the marketplace or any other things. It is a type of interaction with AWS. I would rate this product 9.5 out of 10.

I am currently working with AWS CloudWatch, EventBridge, Lambda functions, and DynamoDB. 

On the development side, I use AWS CDK, the Cloud Development Kit. I use it mainly in our cloud infrastructure, and it has been a significant part of my work.

One of the most valuable aspects of CDK is its ability to integrate various components seamlessly, such as Lambda functions, API Gateway, DynamoDB, and EventBridge. It feels almost like working in a local environment. 

CDK has greatly improved my workflow by reducing boilerplate code and enhancing maintainability with custom constructs. Its integration capabilities with other AWS services, such as EventBridge and DynamoDB, work seamlessly together, something I haven't experienced with other platforms.

There is room for improvement in the use of EventBridge and the initial setup of CDK, which can be a bit challenging. The IAM policies could be simplified to make the setup process more straightforward. AWS could also improve the transparency of Lambda's internal processes and provide more visibility into Lambda logs.

I have been working with AWS CDK for about a year and a half.

CDK is very resilient, and I have not experienced any downtime or significant stability issues.

CDK is scalable, however, it can be expensive. It can scale to millions of users, but it is not the most cost-effective solution.

I have not personally contacted AWS support. I have seen a couple of tickets related to CDK. However, I did not escalate any questions myself.

Positive

Previously, I worked with Microsoft Azure, however, it was more challenging to integrate various services. AWS CDK offers seamless integration, which was a significant factor in choosing it for cloud computing.

The initial setup was complex and took about a week. IAM policies added difficulty, but using a framework like Serverless could simplify this.

The initial implementation involved a team of 12 developers at the first startup I worked for. In my current company, there are above 100 developers involved, with abundant resources.

I have seen measurable benefits from CDK. It allows me to integrate and utilize cloud resources efficiently. There is no other way I could have replicated the success I've had with CDK.

Over time, I expect AWS to become more cost-efficient and resilient. Although the pricing is currently high, I hope they continue to improve their system, which will lead to cost reductions.

During the evaluation process, I considered Azure, but AWS CDK's seamless integration made it the better choice.

I would definitely recommend CDK to others planning to integrate several components on a platform, especially an event-driven architecture. It is one of the best tools available for cloud computing. 

I rate CDK an eight out of ten due to the unavailability of the Ross language in CDK.

My primary use case involves developing backup and front desk applications within my environment. I rely on the product for infrastructure as code, utilizing its capabilities to build the complete infrastructure for DLP applications.

They could allow combining multiple languages, such as JavaScript and Python for the platform. At present, we can use only one language.

There could be a possibility of building infrastructure offline, in a Docker instance, for debugging and testing purposes. At present, it takes two minutes to complete the deployment. However, it takes a lot of time to repeat the process in case of any mistakes or errors. Thus, it would be easier to test the code offline.

We encountered a limitation with the WebSocket API in AWS, specifically regarding the absence of binary coding. It consumes a lot of bandwidth while transforming binary data to base64.

We have been using AWS CDK for one year.

It is a stable platform. I rate the stability an eight out of ten.

We refer to the technical support articles online. They could provide an enhanced documentation.

The initial setup requires prior experience working with it. I rate the process a five out of ten.

AWS CDK has notably streamlined the deployment process compared to other methods, primarily by defining cloud infrastructure as code. However, I have encountered challenges integrating CDK with GitLab for a complete CI/CD pipeline. Currently, manual deployment is required, which diminishes the automated efficiency. 

We don't have to create texts manually using AWS CDK. We can use the construct feature to create texts online but cannot remove certain items from the stack.

We can build multiple stacks simultaneously. It allows us to ensure we do not provide unnecessary permission to certain services. Additionally, deploying for free or within a cost-effective range is particularly beneficial for small companies. However, we have to pay for other services, such as routers, which are more expensive than MongoDB. It costs more for smaller applications with less traffic.

I rate it a seven out of ten.

We use AWS CDK for defining infrastructure as code.

You can use AWS CDK to write code to provision infrastructure. The solution has a significant quality of life improvement for software developers who can code to spin up infrastructure on AWS.

Using AWS CDK requires some knowledge of popular programming languages.

I have been using AWS CDK for over three years.

AWS CDK has good stability.

AWS CDK is an easy-to-scale solution.

The solution's customer support is average. The only way to get support is to go to GitHub and raise an issue. Then an engineer will look into it and roll out a fix, which usually takes time.

Neutral

The solution’s initial setup is easy.

AWS CDK can be deployed in minutes. One engineer is enough to deploy the solution if he knows about the AWS cloud. However, if the engineer isn't skilled in the AWS cloud, one architect and an engineer would be required for the deployment. One person is enough to maintain the solution and keep up to date with the latest CDK releases.

Since AWS CDK is an open-source solution, it's free to use.

The solution has a lot of community documentation, and you'll get first-class support compared to the other programming languages.

Overall, I rate AWS CDK a nine out of ten.

The most valuable features of the AWS Cloud Development Kit (CDK) are its speed and ease of deployment. We can quickly deploy infrastructure by writing code.

At the beginning, there were some issues regarding different plugins.

We have been using AWS Cloud Development Kit (CDK) for 6-8 months.

It is a stable product. We've transitioned from using tools like Terraform and found AWS CDK quite useful, particularly in managing cloud permissions and infrastructure.

The initial setup process was easy. All that was required was to install the NPM packet for AWS CDK, and after that, it was ready to be used.

If you're considering using CDK, it's advisable to familiarize yourself with programming languages such as Python. It operates effectively with active vendor licenses.

I rate it a seven out of ten.

We primarily focus on cloud development and migration. We have customers from the banking and finance sector. We find AWS CDK to be particularly useful for migrating existing systems to the cloud. This involves transferring, modifying, or upgrading these systems to make them cloud-compatible.

The value proposition of AWS CDK varies depending on the customer's needs. However, some common aspects that customers appreciate include backup functions, price, and DevOps integrations.

The primary issue we've encountered is pricing. Some customers find the pricing to be somewhat high.

Additionally, there's a discrepancy between the promised resource utilization and the actual utilization. The resource utilization calculations don't align with the provided guidelines. So, the pricing and resource utilization calculations could be refined.

We've been working with AWS CDK for over one year now.

Downtime has been minimal. It is very stable. 

I would rate the scalability a nine out of ten. No issues with scalability. 

It is suitable for medium and large businesses. 

We get good support. We have a POC where we can raise a ticket and get support.  They do a lot of hand-holding and provide training. Everything from response time to quality of response is good. 

Positive

We have primarily used AWS CDK for our cloud development projects.

We have encountered competition from local vendors in various regions while supporting clients worldwide. This competition mainly focuses on pricing rather than technical aspects.

The choice depends on the specific needs and preferences of the client. We have successfully implemented projects using both AWS CDK and Azure Resource Manager.

The setup process is very straightforward. AWS CDK supports deployments to both private and public cloud environments.

I would rate AWS CDK a nine out of ten. We are very satisfied with its capabilities and ease of use.