Provisioning - AWS_CDK vs Troposphere vs Stacker

Question

Troposphere is a python project for AWS provisioning. This is a mature project.

AWS CDK is still in developer preview.

cdk diff does help on ease of state maintenance before cdk deploy. Am not sure, how troposphere helps us on state maintenance? except generating a cloudformation template...

From AWSEvent talk, it is mentioned that, abstractions are not built-in for using Troposphere

where as

AWS CDK has good abstractions.

CDK enables CI/CD, easily, where-as Troposphere needs extra automation to upload CF templates

We need to take a decision on picking one, to provision our infrastructure on AWS

---

From the aspect of state maintenance, software best practice, code maintenance & supported resource types, CI/CD(end-to-end automation) for provisioning,

What are the advantages of AWS_CDK vs Troposphere vs Stacker? being open to any programming language..

Answer 1

troposphere is part of what CDK does, a more apt comparison would be stacker (https://stacker.readthedocs.io/en/latest/ which uses troposphere -- I'm a maintainer of both) vs CDK. Let me know if you have any other questions!