# Infrastructure as Code A fundamental principle of DevOps is to treat infrastructure the same way developers treat code. The Application code has a defined format and syntax. If the code is not written according to the rules of the programming language, applications cannot be created. The Code is stored in version management or source control system that logs a history of code development, changes, and bug fixes. When code is compiled or built into applications, we expect a consistent application to be created, and the build is repeatable and reliable. Also, it's a way to manage: * Configurations * Provisioning * Deployments The Tool from software development applied to infrastructure: * Version Control. * Testing. * CI / CD pipelines. ### Benefits * **Cost reduction**: Speaks to less time spent by people and effort * **Speed:** Automation-enabled speed through hast execution with more visibility. * **Less risk:** Less chance of human error, manual misconfiguration which increases reliability and decreases downtime and improves security. ![](https://1098627933-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJLSyDhjobJQWwESFD5%2F-MKWRWobMYc23PKQzYmn%2F-MKWWkv2SpzKmdzNIRB2%2Fimage.png?alt=media\&token=0a42c5c6-04b2-4307-aafa-7cf59876b81f) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://ctreminiom.gitbook.io/docs/aws-cloudformation/infrastructure-as-code.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.