Answers are grounded in this paper and cite their sources.
Infrastructure-as-code (IaC) has become a primary means of managing cloud infrastructure for enterprises‚ but studies have shown that IaC configurations do not necessarily reflect actual deployed environments (Hassan et al․‚ 2024; Rahman et al․‚ 2023)․ This paper explores factors contributing to mismatches between IaC configurations and deployed environments and ways to prevent these mismatches‚ in addition to methods of detecting them․ Review of sixteen sources on IaC theory (Morris‚ 2021) and practice‚ including studies of IaC errors and misconfigurations (Rahman et al․‚ 2020‚ 2023; Hassan et al․‚ 2024)‚ and other relevant practices (Kumara et al․‚ 2021)‚ as well as the author's experience leading an enterprise-wide‚ multiunit cloud migration initiative in financial services‚ led to development of a three-part governance approach for IaC environments: pre-deployment policy checks‚ ongoing drift monitoring‚ and immutable infrastructure deployment strategies․ The paper discusses appropriate uses for each approach․ Studies and the author's experience show that predeployment policy checks are not sufficient to prevent IaC misconfigurations because many postdeployment changes to environments occur outside IaC (Falazi et al․‚ 2023)․ Ongoing drift monitoring can help fill gaps left by predeployment policy checks‚ but only if the tools used for drift monitoring are reliable․ Immutable infrastructure deployment strategies can help prevent IaC misconfigurations by making it more difficult to make postdeployment changes to environments․ Overall‚ the paper recommends a multi-layered approach to IaC governance for enterprises and notes known limitations of relying solely on predeployment policy checks.
No takes yet. Share an insight, caveat, or question.
Sri Harsha Mogali (2026) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: