7 ms·
A Public Registry for AWS CloudFormation
- yazaddaruvala 5y agoThe biggest issue with CF and CDK is the lack of support for features when they launch in the CLI and WebConsole. One controversial opinion: I feel AWS should reduce surface area and deprecate the CLI in favor of CDK (requiring CDK support for launching a new service and/or feature). To emulate the deprecated AWS CLI, developers can write/edit "CDK scripts" that are uploaded via an AWS CLI-lite. Disclaimer: I work at Amazon, but not on AWS and have no insight or influence over anything AWS does. Please read this as "just another developer who uses AWS".
- philliphaydon 5y agoAh I just can't get into the CDK. I much prefer just writing the JSON Cloudformation and executing it via the cli...
- robertkoss 5y agoSame, I'd love to see more support on Cloudformation and projects like SAM
- dkdk8283 5y agoYes the CDK is a major step backwards. Just because you can reduce reuse doesn’t mean you should. Operations is an exercise in complexity management, not feeling smart.
- yazaddaruvala 5y agoSure, I’m happy for other people to use CF over CDK. I mostly mean to say AWS doesn’t need a full featured CLI. Devs should just use CF/CDK through a CLI-lite. That also force AWS to block feature launches till CF supports them.
- arpinum 5y agoWhen API keys are involved, I need a lot more confidence in the security of the software than what I am seeing so far. I'm willing to trust Datadog for configuring their own services, but the community providers scare me from a security perspective. What I can see from the early uploads are community providers accessing secrets manager to fetch API keys. What happens when a provider requests permissions for all secrets? How well will the UI surface broad permission grants? What if providers bake in "telemetry" to spy on me ?
- rjzzleep 5y agoCan someone explain to me if people still do new projects using CloudFormation? If so why? I'm in an enterprise and they do everything with CloudFormation, but it doesn't really make sense to me. None of the code is reusable, it's yaml or json, which isn't easy to write to begin with. I remember in the early days there were 2 frameworks that would compile to CF. I googled recently and found Lono, and it looks nice, but there's a fraction of the modules available that are available for terraform and getting help is also limited by the number of users. And then there is the big question for me why are building things that make CF look like Terraform[0]. I'm not a fanboy of Terraform either, there's plenty of stuff that I didn't like about it. But even AWS themselves almost seem to have more reusable templates in Terraform than they do CF. [0] https://lono.cloud/ https://lono.cloud/
- blowski 5y agoIf you've spent the last 7 years writing CloudFormation scripts, why would you bother switching? If you're starting from scratch today, though, i agree that Terraform is better for most use cases.
- zoover2020 5y agoCDK is backwards compatible with CFN templates and could act as a drop in replacement. IaC improves DX and saves so much more time, compared to debugging JSON/YML.
- blowski 5y agoI haven't used CDK - you recommend it over Terraform then?
- nuker 5y ago> writing CloudFormation scripts templates, not scripts, Declarative. And CFN is much more lean and reliable than TF, I recommend it for new to AWS people.
- 5y ago