When using Terraform instead of Cloudformation on AWS, I usually get immediate feedback on the terminal, which makes the work very productive.

With CloudFormation, however, I tend to edit the file in my computer, upload it to Cloudformation console on AWS, and keep watching until I get an error/success. Even using CI/CD is not much of an advantage, as the result is usually ROLLBACK_COMPLETE, and I have to go to the console to see what went wrong.

I'm I following the right workflow for Cloudformation? Should I be doing things differently?

closed as off-topic by Robert Harvey Sep 1 at 0:21

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions asking for assistance in explaining, writing or debugging code, or using coding tools, are off-topic here. These can be asked on Stack Overflow if they include the desired behavior, a specific problem or error, and a Minimal, Reproducible Example of the problem." – Robert Harvey
If this question can be reworded to fit the rules in the help center, please edit the question.

  • Given that you're clearly happy using the command-line, why are you using the console for CloudFormation? – Philip Kendall Aug 1 at 20:31

Using the AWS CLI for CloudFormation from the terminal would be definitely quicker than clicking around in the AWS Console. Having said that, on occasions, I find it easier and quicker to go to the AWS Console to examine CF events than using the command line.

Not the answer you're looking for? Browse other questions tagged or ask your own question.