AWS Cloud Development Kit (CDK)

Name: AWS Cloud Development Kit (CDK)
Brand: Amazon Web Services (AWS)
Rating: 4.4 (125 reviews)

Leader

Official Global LinkedIn page for Amazon Web Services (AWS).

Est 2006|Valuation $2560B|3 Ref Customers

LinkedIn 10.9M|Website|Web traffic 1.1M|FTEs 148,001|HQ Seattle, Washington, US

MarketsInfrastructure as Code (IaC)

AWS Cloud Development Kit (CDK) screenshot

01Competitive Landscape

Narrative analysis

#### Where AWS CDK is commonly used - AWS-only application stacks where L2/L3 constructs reduce duplication and encode AWS patterns. - Internal platform libraries and construct-based reuse to enforce organization standards. #### Where Terraform is often chosen - Multi-cloud deployments and extensive third-party integrations due to a broad provider ecosystem. - Workflows that require explicit state-centric operations and certain refactors or migrations. #### Where Pulumi is often chosen - Teams that want language-first IaC with multi-cloud support and integrated collaboration/state features. #### Customer-reported comparisons - Community discussions include both pro-CDK and pro-Terraform perspectives: some users emphasize CDK's AWS-specific higher-level constructs, while others emphasize Terraform's import/state/refactor capabilities and broader ecosystem.

Adoption trends

Evidence here is qualitative: community discussions and GitHub activity indicate ongoing interest and active maintenance. AWS CDK repository activity and a public roadmap are signals of continued development, but no authoritative market-share statistic was identified in accessible sources.

	AWS CDK	Terraform (HashiCorp ecosystem)	Pulumi
Starting Price	Open-source framework; pay for AWS resources; CloudFormation-related usage charges may apply for third-party hooks/providers	Open-source core; enterprise offerings available with vendor-published pricing	Published individual and paid tiers; vendor-published pricing available
Typical Use Case	AWS-first teams using language-based IaC targeting CloudFormation	Multi-cloud and broad provider coverage; workflows that benefit from explicit state management	Language-first IaC for multi-cloud use; managed collaboration and state in Pulumi Cloud or self-hosted options
Key Strength	Developer-oriented language constructs and a growing construct ecosystem; close alignment with AWS service models	Broad provider ecosystem; mature state management and plan/apply workflows	Language-first IaC with multi-cloud support and collaboration features via managed services
Key Weakness	Dependent on CloudFormation semantics and limitations; AWS-centric	HCL learning curve for some teams; enterprise features may add cost/complexity	Managed features may incur costs; dependency on Pulumi service for some collaboration workflows unless self-hosted

01Competitive Landscape

Narrative analysis

Where AWS CDK is commonly used

AWS-only application stacks where L2/L3 constructs reduce duplication and encode AWS patterns.
Internal platform libraries and construct-based reuse to enforce organization standards.

Where Terraform is often chosen

Multi-cloud deployments and extensive third-party integrations due to a broad provider ecosystem.
Workflows that require explicit state-centric operations and certain refactors or migrations.

Where Pulumi is often chosen

Teams that want language-first IaC with multi-cloud support and integrated collaboration/state features.

Customer-reported comparisons

Community discussions include both pro-CDK and pro-Terraform perspectives: some users emphasize CDK's AWS-specific higher-level constructs, while others emphasize Terraform's import/state/refactor capabilities and broader ecosystem.

Adoption trends

Evidence here is qualitative: community discussions and GitHub activity indicate ongoing interest and active maintenance. AWS CDK repository activity and a public roadmap are signals of continued development, but no authoritative market-share statistic was identified in accessible sources.

	AWS CDK	Terraform (HashiCorp ecosystem)	Pulumi
Starting Price	Open-source framework; pay for AWS resources; CloudFormation-related usage charges may apply for third-party hooks/providers	Open-source core; enterprise offerings available with vendor-published pricing	Published individual and paid tiers; vendor-published pricing available
Typical Use Case	AWS-first teams using language-based IaC targeting CloudFormation	Multi-cloud and broad provider coverage; workflows that benefit from explicit state management	Language-first IaC for multi-cloud use; managed collaboration and state in Pulumi Cloud or self-hosted options
Key Strength	Developer-oriented language constructs and a growing construct ecosystem; close alignment with AWS service models	Broad provider ecosystem; mature state management and plan/apply workflows	Language-first IaC with multi-cloud support and collaboration features via managed services
Key Weakness	Dependent on CloudFormation semantics and limitations; AWS-centric	HCL learning curve for some teams; enterprise features may add cost/complexity	Managed features may incur costs; dependency on Pulumi service for some collaboration workflows unless self-hosted