Changes

At Amazon AWS, they have a product called CloudFormation (an alternative, subscription-based model to Beanstalk) which provides a declarative template-based Infrastructure as Code model for configuring AWS. The value of Infrastructure as Code can be broken down into three, measurable categories: Cost (reduction), Speed (faster execution), and Risk (remove errors and security violations).

== Comparison to QualityBox ==The value of Infrastructure as Code can be broken down into three, measurable categories: Cost (reduction), Speed (faster execution), and Risk (remove errors and security violations). With [[QualityBox]], we approach Infrastructure as Code (IaC) with all three types: declarative (functional), imperative (procedural) and intelligent (environment aware). These can be easily summarized as 'What', 'How' and 'Why'. That is to say that we define ***what*** the eventual target configuration should be. We define ***how*** the infrastructure should be changed to meet this. (Given A, how do we get to A'; or even B). And we even determine the 'what' with intelligence about existing work-loads, co-dependent applications, or other parameters that would dictate the preferred end state ''before'' we execute any changes. <ref>More at [[wp:Infrastructure as Code]]</ref>