AWS CloudFormation

Best Iaas tool in the market.

Comentarios: AWS CloudFormation has all the capabilities that many DevOps tools have.

Puntos a favor:

For streaming purposes, I'm using it to build a clustering solution. It is the greatest tool for delivering packages, especially because the AWS CloudFormation template includes settings for Lambda, Sagemaker, and other services.

Puntos en contra:

There is nothing wrong with this tool, but there is a need for development in terms of setting dependencies between two stacks.

The best IAC tool for AWS Cloud

Comentarios: 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

Puntos a favor:

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.

Puntos en contra:

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

Great cloud templating solution for AWS.

Puntos a favor:

Very comprehensive and low level schema that allows capability to template up the desired cloud solution

Puntos en contra:

Cloudformation can sometimes fail to update stacks due to drift issues. Have to be extra cautious changing some resource parameters, can cause 'new' instances to of the resources to be created instead of updating the existing resource.

Not enough compelling reasons to use over Terraform

Comentarios: CloudFormation may be ideal for you if you're a 100% AWS shop and have no intention whatsoever of looking at outside products. However, consider the vibrant community that Terraform has. It's a real alternative, and AWS has even picked up development of the Terraform provider for AWS.

Puntos a favor:

CloudFormation, like many other services, is designed for AWS from the ground up. It's supported by the developers, and it shows in how you're able to roll back changes, etc, which can't be done with Terraform.

Puntos en contra:

The syntax is significantly more confusing (to me) than Terraform. HashiCorp's HCL makes it a lot easier to write and visualize what I'm trying to create. CloudFormation only works on AWS; if you'll be working on anything else, you'll have to learn a different tool.

Valuable tool for DevOps and infrastructure engineers

Comentarios: CloudFormation had a bit of a learning curve, but once we laid out these foundations, the development, debugging, and deployment became faster and more reliable.

Puntos a favor:

CloudFormation helped us build our infrastructure quickly and reliably on AWS. Without much knowledge about infrastructure or AWS, we could use the documentation, references, and code samples of CloudFormation stacks provided by AWS and the OSS community to build our infrastructure. Instead of navigating AWS Console and being confused, we could copy/paste the resource name or configuration property to Google and quickly know what it's for and how to use it. Sharing knowledge among team members is automatic since anyone can look at the code to see the current state of the infrastructure. CloudFormation will save you plenty of time if you have multiple environments for your application. You create one template and use it for all of your environments, knowing that they will behave as expected.

Puntos en contra:

CloudFormation templates cannot have complex logic, making them easy to understand, but this limited logic support sometimes forced us to create separate files for our development and production environments.