Loading content
The AWS Cloud Development Kit (AWS CDK) is an open-source framework for defining cloud infrastructure in familiar programming languages. It synthesizes CloudFormation templates from high-level constructs, enabling reusable infrastructure, composition, and testing. CDK accelerates provisioning while integrating with AWS services and CI/CD pipelines for repeat…
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
AWS CDK is an open-source framework that lets you define AWS infrastructure in familiar programming languages. It synthesizes CloudFormation templates from higher-level constructs and turns them into deployable stacks.
AWS CDK was developed by Amazon Web Services to define infrastructure not just with declarative templates, but with the expressive power of programming languages. A first developer preview was announced in 2018 at AWS Summit New York; general availability followed in 2019, and AWS CDK v2 in 2021 with a consolidated Construct Library.
Think in three layers: you describe constructs in your programming language, those building blocks are synthesized into a CloudFormation template, and CloudFormation applies it as stacks in AWS. That keeps infrastructure versioned and testable without writing every resource as a separate template.
Infrastructure is described, versioned, and reviewed like software.
Reusable building blocks bundle resources, configuration, and best practices.
CDK code is translated into an AWS CloudFormation template.
CloudFormation creates, updates, and deletes the target resources in AWS.
Stacks are the deployment units that are created, updated, or deleted together.
The CLI and library drive synthesis, diffing, and deployment of CDK applications.
CDK is useful when teams want to manage AWS infrastructure with the same practices used for application software: code review, tests, reuse, and pipeline deployments. It is especially strong for complex, recurring AWS architectures. Limits: the extra synthesis layer must be understood, errors often surface only at CloudFormation deploy time, and the model remains tied to AWS and its resource semantics.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.