AWS CloudFormation vs. vmgen

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

vmgen is a great solution because it's very simple and easy to use. It doesn't have many features, but that makes it clear and uncomplicated

• SaaS
• Paas
• Iaas
• On promises

Incentivized

• virtual machines
• IaaS
• cloud computing

• 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

• number of features
• support
• BGP

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

vmgen is simple and intuitive, has clear pricing and is easy to use. We didn't need to employ a DevOps Engineer to configure it. The cost of vmgen is predictable and cost-effective.

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

Incentivized

• reduced cost of infractructure
• reduced cost of maintanance
• improved productivity