Question 1

How do I avoid expensive defaults in AWS CDK constructs?

Accepted Answer

The guide warns about defaults like NAT gateways in VPCs and suggests reviewing construct properties or using overrides. For example, it provides a cost breakdown for idle NAT gateways to emphasize the impact.

Question 2

Open CDK guide vs official AWS CDK docs: which should I use?

Accepted Answer

Use both: official docs for API reference and foundational concepts, but Open CDK for practical, real-world advice on pitfalls and best practices that official docs often omit. It complements rather than replaces AWS documentation.

Question 3

What's the best way to structure multiple stacks in CDK?

Accepted Answer

The guide recommends separating stacks into 'outer' (e.g., foundation, service) and 'inner' (e.g., monitoring, database) components. This mental model helps manage dependencies and scale applications effectively.

Question 4

How to handle secrets and configuration in CDK projects?

Accepted Answer

Store secrets in SSM or Secrets Manager and reference them in cdk.json. Avoid CloudFormation parameters for better validation, and use stage-scoped context variables to manage different environments.

Question 5

Is the Open CDK guide regularly updated?

Accepted Answer

Yes, it's a living document maintained by the community, with contributions encouraged via GitHub pull requests. However, updates depend on volunteer efforts, so some sections may lag behind CDK releases.

Question 6

What are common CDK deployment pitfalls?

Accepted Answer

The guide lists issues like cdk diff exiting with error codes, lack of MFA support, and the need to version control CloudFormation templates. It suggests workarounds like using aws-vault and including diff output in code reviews.

Open CDK Guide

What is Open CDK Guide?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions