Infrastructure as code: Difference between revisions

Revision as of 15:44, 7 June 2016

Revision as of 01:01, 21 July 2016

Line 1:

'''Infrastructure as Code''' ('''IaC''') is the process of managing and provisioning computing infrastructure (processes, [[bare-metal server]]s, [[virtual servermachine|virtual servers]]s, etc.) and their configuration through machine-processable definition files, rather than physical hardware configuration or the use of interactive configuration tools.<ref name="AWS in Action, IaC" /> The definition files may be in a [[version control system]]. This has been achieved previously through either scripts or declarative definitions, rather than manual processes, but developments as specifically titled 'IaC' are now focused on the declarative approaches.

Infrastructure as Code approaches have become increasingly widespread with the adoption of [[cloud computing]] and [[Infrastructure as a Service]] (IaaS). IaC supports IaaS, but should not be confused with it.<ref name="AWS in Action, IaC" />