AWS CloudFormation Best Practices

Re:AWS CloudFormation Best Practices by otterley on Wednesday March 31, 2021 @02:44PM (#26651287)

AWS solutions architect here! (Opinions are my own and not necessarily those of my employer.)

Many of us now believe that CloudFormation is best described as the assembly language of AWS infrastructure: you can hand-code it, but it's challenging and verbose, and there's a lot of detail you have to get involved in.

CDK is the high-level solution to this challenge. With CDK you describe your infrastructure in terms of high-level constructs such as classes. Your stacks are described as applications instead of YAML templates. You can use many different programming languages including TypeScript and Python, and code is reusable. You can even vendor custom construct libraries to share within your org, or openly via npm.

I've become a convert since CDK came out - it's been ages since I've handwritten CloudFormation templates.

https://aws.amazon.com/cdk/

[ Parent | on HN ]

Re:AWS CloudFormation Best Practices by throwaway894345 on Wednesday March 31, 2021 @03:35PM (#26652015)

Yeah, I haven't given CDK a good shot yet. I did write something like it (for Python) before CDK existed, and it was very nice. I'd like to play with CDK, but I'm no longer working on AWS systems but rather GCP/Terraform. Best of luck to the CDK folks!

[ Parent | on HN ]

Re:AWS CloudFormation Best Practices by twg_jack on Wednesday March 31, 2021 @03:08PM (#26651639)

I'll second CDK -- love it and it's so much easier than writing raw CFN.

[ Parent | on HN ]