aws/aws-cdk

The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 26 minutes ago
Added to GitGenius on September 4th, 2026
Created on October 4th, 2017
Open Issues & Pull Requests: 2,871 (+2)
GitHub issues: Enabled
Number of forks: 4,626
Total Stargazers: 12,889 (+0)
Total Subscribers: 212 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

AWS CDK is an infrastructure-as-code framework that lets developers define cloud infrastructure using programming languages and provision it through AWS CloudFormation.

The tool addresses the challenge of managing AWS infrastructure by providing high-level object-oriented abstractions instead of writing CloudFormation templates directly. Developers write infrastructure code in their language of choice—TypeScript, Python, Java, .NET, or Go—and the CDK synthesizes this into CloudFormation templates for deployment. The framework includes a library of reusable constructs that encapsulate AWS best practices, reducing boilerplate and allowing teams to share infrastructure patterns across projects.

Teams should adopt the CDK if they prefer writing infrastructure in general-purpose programming languages rather than YAML or JSON templates, and if they want to leverage existing language ecosystems and testing frameworks for infrastructure code. It suits organizations already invested in AWS and those building complex, multi-component deployments where code reuse and abstraction matter. The tool is particularly valuable for teams that want to apply software engineering practices like version control, unit testing, and code review to their infrastructure definitions.

The project maintains active development across multiple language bindings and receives regular updates to support new AWS services. The framework includes a CLI for synthesizing templates, deploying stacks, and comparing changes before applying them. The project publishes comprehensive API documentation and maintains a public roadmap for planned features.