providing a configuration, provisions the cloud resource as required very instantly. saves a lot of time. can also export existing resource as configuration

can provide integrations with ide tools like extension for VS Code for even simpler interface.

If your entire infrastructure is in AWS cloud, then this is the best IAC tool. I would say even better than Terraform in certain aspects if you are not aiming multicloud or hybrid cloud

It is easy to provision AWS resources and update them. It supports rollback. It also allows seeing the changes that will be applied using changesets. It is transactional , either all the resources are updated or none are.

The error messages when running the Cloudformation stacks are sometimes not easy to decipher.

1. I make the best out of CloudFormation for performing all my Infra-Implementations in my Dev, QA, Pre-Prod & Prod Environments. 2. It has amazing community support from which I can refer and practice best strategies for my deployments. 3. For detailed clarification regarding the features, excellent customer service support is provided by AWS. 4. It has a well-designed Documentation which helps me to effectively use the features and integrate with other AWS services. 5. The cost management by making use of its Stack creation is marvelous and no resource will be running in the background once you've decided to delete the stack. 6. For automation of multiple resources, I make use of combining CloudFormation with CodePipeline so that I can deliver my resources without any compromise in its integrity or configurations.

1. AWS CloudFormation offers me a spectacular platform to build and provision my organization's infrastructure requirements. 2. It provides me the feature of automation with various DevOps software seamlessly. 3. The compliance standards followed for each resource creation is top notch. 4. I can create, modify or delete the stack which is derived from my CloudFormation Template with ease. 5. It brilliantly integrated with multiple third-party software such as Git, Jenkins, Ansible, Docker, Kubernetes through its fascinating API functionality.

1. Once you create the stack in CloudFormation, you won't be able to change the name of the stack. 2. Deep understanding about the usage of scripts is required in order to establish connection with other resources. 3. For troubleshooting, the tracking of error logs in the associated CloudWatch entries is quite challenging in CloudFormation.

So far it has served us well, but we are moving to CDK in the near future

- Templates are written in a YAML subset, which is arguably preferable to JSON - It provides many options to properly manage the stacks lifecycle - When coupling with Cloud Development Kit, it makes up for a powerful IaC solution for AWS - As with any other AWS service, you can manage CloudFormation in the best way that fancy your team needs

- It's hard to understand that some resources that are possible to tag, don't support tagging in the templates - Templates can get complex over time

we can automate provisioning and decommission as well

We didn’t find any difficulty in using cloud formation