AWS CloudFormation vs. AWS Systems Manager

AWS CloudFormation is well suited for scenarios where all of your resources need to be provisioned on AWS but it is not suited for hybrid cloud deployments. It's very easy for someone new to learn. The level of customization offered as part of the template specifically for AWS services is great. There is also a UI tool where we can drag and drop the services we want and it generates an yaml file which is very easy to use. The visibility of stacks and its resources and one place where we can track and identify the issues in deployment is great.

Incentivized

When you have a process running in aws that needs to copy files to group of instances as part of the process Installing software on a group of machines Adding Cloudwatch agent to instance.

Incentivized

• SaaS
• Paas
• Iaas
• On promises

Incentivized

• Copy files to a group of instance with particular tag
• Enable CW agent and push metrics to CW
• Easy to install software in a group of instances.

Incentivized

• Error Description upon Failure Needs to be Improved.
• Slow to create, delete or update.
• Need to delete resources manually. It can ask before starting deletion whether to skip those resources or delete them.

Incentivized

• I would like to see the Search feature improved a bit more.
• UI is little bit confusing initially

Incentivized

We didn't look into anything else as Cloudformation was "built-in" for AWS, it just kind of made sense to go with that. Terraform was something that we briefly looked into Terraform but decides to stick with Cloudformation because our task was relatively "simple". Apparently if it's a bit more complex, Terraform might be the way to go.

Incentivized

• It has a positive ROI
• Less time inverted in bugs
• More stable source code

Incentivized

• Reduced team's time spent on EC2 management
• Patch management
• Remote access

Incentivized