AWS CDK Day 2023 - CDK Best Practices

preview_player
Показать описание

AWS CDK revolutionized the way we create resources in the cloud. It enables developers to write infrastructure as code and feel at home.

However, AWS CDK is such a flexible and powerful tool that it's easy to make mistakes. And some errors can be very costly.

I'll cover topics such as:
1. Recommended project Structure and stack guidelines
2. Constructs guidelines - how to model constructs. I believe in domain-driven constructs.
3. CI/CD guidelines - handling configuration per environment and secrets in CDK.
4. Resiliency & security guidelines
5. General development tips - tags, working with CFN resources, and more.

Рекомендации по теме
Комментарии
Автор

Thanks! Very clear and straight to the point!

sonic_boom
Автор

Thank you for the experience. About one stack is questionable. I am using Stages to group stacks. Separate stacks with storage and application by criticality (in case if stack with Lambda fails I don't want to allow DB stack to fail) and by frequency of deployment (I am not changing for example RDS a lot so I don't want to touch this stack.)

artemvolkov
Автор

So, am I wrong when into the same project I create two Stacks?

richardferneygarcia
visit shbcf.ru