<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Infrastructure as Code(IaC) in DevOps ecosystem - Medium]]></title>
        <description><![CDATA[With IaC, DevOps teams can enable the operations team to develop and install environments by restoring configurations and deploying them on the go, every single time. This ensures that the project teams always have their deployment setups intact without environment drift. - Medium]]></description>
        <link>https://medium.com/infrastructure-as-code-iac-in-devops-ecosystem?source=rss----20e8a4d968d4---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Infrastructure as Code(IaC) in DevOps ecosystem - Medium</title>
            <link>https://medium.com/infrastructure-as-code-iac-in-devops-ecosystem?source=rss----20e8a4d968d4---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:46:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/infrastructure-as-code-iac-in-devops-ecosystem" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Infrastructure as Code (IaC) in DevOps and Cloud ecosystem]]></title>
            <link>https://medium.com/infrastructure-as-code-iac-in-devops-ecosystem/infrastructure-as-code-iac-in-devops-and-cloud-ecosystem-d3a3e0c20ce7?source=rss----20e8a4d968d4---4</link>
            <guid isPermaLink="false">https://medium.com/p/d3a3e0c20ce7</guid>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[iac]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[iaas]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Jitander Kapil]]></dc:creator>
            <pubDate>Tue, 27 Oct 2020 11:59:42 GMT</pubDate>
            <atom:updated>2020-10-27T11:44:52.882Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*gI7nYpjtjhiGChbOwuxZVA.png" /><figcaption><strong>Infrastructure as Code</strong></figcaption></figure><p><strong>Infrastructure as Code, Configuration templates, and Need of such Offerings.</strong></p><p>In order to achieve the absolute potential that an ideal DevOps implementation promises, the work profiles of the stakeholders have to be fluid; a developer should be able to build and run their own infrastructure including their environment necessities and the operations team should be empowered to understand the product and identify the gaps and errors, whenever warranted.</p><p>The concept of <strong>Infrastructure as Code (IaC)</strong>, aka programmable infrastructure, stems from this necessity and compiles the many dimensions of infrastructure requirements across a project lifecycle into a few lines of code.</p><p>With IaC, DevOps teams can enable the operations team to develop and install environments by restoring configurations and deploying them on the go, every single time. This ensures that the project teams always have their deployment setups intact without any risk of environment drift in release pipelines.</p><p>IaC, as a DevOps concept, is steadily gaining popularity among the masses; a report from Forrester Research titled “Infrastructure as Code: Fueling the fire for faster application delivery” reported that IaC removes friction in several steps of the SDLC and fosters better collaboration between Dev and Ops team. While the report concluded that IaC has now become the accelerator to create a more collaborative and integrated software delivery organization, it also advises that IaC tools alone cannot make it possible. The report recommends the combination of the latest IaC tools, collaborative processes, and proper skills transfer for the complete DevOps realization.</p><h4><strong>Infrastructure-as-code (IAC) tools and offerings:</strong></h4><p>IAC tools fall under two umbrellas: <strong>configuration orchestration</strong> and <strong>configuration management</strong>. Many products on the market, whether commercial or open-source, offer both functions.</p><p>Configuration-<em>orchestration </em>tools include AWS CloudFormation and Terraform. Such tools are designed to automate the deployment of servers and other infrastructure. Configuration-management tools like Chef and Puppet are designed to help configure the software and systems on a provisioned system.</p><p>When selecting a tool, you should consider the target deployment. For example, AWS CloudFormation is designed to provision and manage infrastructure on Amazon Web Services only. Which makes sense — why would AWS support Google Cloud Platform? Of course, that’s not always the case: Red Hat’s Ansible runs on a variety of platforms, not just Red Hat Enterprise Linux.</p><p>Third-party tools like Puppet and Chef work with on-premises servers and multiple cloud providers infrastructure-as-a-service offerings. Cloud-focused Terraform is cloud-agnostic, letting you automate infrastructure stacks from multiple cloud service providers simultaneously and integrate other third-party services.</p><p>While each tool has its own domain-specific language (DSL), the DSL is usually based on YAML and/or JSON. For example, Terraform uses its own DSL called Hashicorp Configuration Language (HCL), which is based on JSON. AWS CloudFormation templates can be created with both YAML and JSON. Chef uses the Ruby language, as does Puppet.</p><p>IaC is made more accessible today through a comprehensive range of tools available for automating the entire provisioning process.</p><h3><strong>Popular IaC offerings:</strong></h3><p><strong>1. Azure Resource Manager (ARM)</strong></p><p>Microsoft’s IaC tool is available for users in the form of Azure Resource Manager. Using this tool, users can provision infrastructure and handle dependencies in one seamless cycle through Azure Resource Manager templates (ARM templates). The resources your template taps into are declaratively described within JSON and you can declare multiple Azure resources in one ARM template to establish whole project environments.</p><p>We can reuse the same template an infinite number of times and always get the same results.</p><p>Use an Azure DevOps or VSTS dashboard to visually monitor all your builds and releases, and get a quick overview of the overall health of your environments and the quality of your templates. The Resource Manager also supports the grouping of server instances and the unified management of groups.</p><p>e.g. Template to generate a unique storage account name.</p><p>{</p><p>“$schema”: “http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#&quot;,</p><p>“contentVersion”: “1.0.0.0”,</p><p>“parameters”: {</p><p>“location”: {</p><p>“type”: “string”</p><p>},</p><p>“accountType”: {</p><p>“type”: “string”</p><p>},</p><p>“kind”: {</p><p>“type”: “string”</p><p>},</p><p>“accessTier”: {</p><p>“type”: “string”</p><p>},</p><p>“minimumTlsVersion”: {</p><p>“type”: “string”</p><p>},</p><p>“supportsHttpsTrafficOnly”: {</p><p>“type”: “bool”</p><p>},</p><p>“allowBlobPublicAccess”: {</p><p>“type”: “bool”</p><p>}</p><p>},</p><p>“variables”: {</p><p>“storageAccountName”: “[concat(uniqueString(subscription().subscriptionId), ‘storage’)]”</p><p>},</p><p>“resources”: [</p><p>{</p><p>“name”: “[variables(‘storageAccountName’)]”,</p><p>“type”: “Microsoft.Storage/storageAccounts”,</p><p>“apiVersion”: “2019–06–01”,</p><p>“location”: “[parameters(‘location’)]”,</p><p>“properties”: {</p><p>“accessTier”: “[parameters(‘accessTier’)]”,</p><p>“minimumTlsVersion”: “[parameters(‘minimumTlsVersion’)]”,</p><p>“supportsHttpsTrafficOnly”: “[parameters(‘supportsHttpsTrafficOnly’)]”,</p><p>“allowBlobPublicAccess”: “[parameters(‘allowBlobPublicAccess’)]”</p><p>},</p><p>“dependsOn”: [],</p><p>“sku”: {</p><p>“name”: “[parameters(‘accountType’)]”</p><p>},</p><p>“kind”: “[parameters(‘kind’)]”,</p><p>“tags”: {}</p><p>}</p><p>],</p><p>“outputs”: {}</p><p>}</p><p>After successful deployment, there is only one storage account in the resource group. The storage account name is a unique string generated by the template.</p><p><strong>2.</strong> <strong>AWS Cloud Formation</strong></p><p>This is specifically designed for users working in the AWS Cloud. CloudFormation allows users to model their infrastructure within a JSON or YAML template file. The service also adds automation features to help with the deployment of resources in a repeatable and manageable way, and you only pay for the resources used — not the service itself. With the template configured to your application specifications, CloudFormation will handle the rest of the tasks for you.</p><p>The use of plaintext is particularly handy. As mentioned, YAML or JSON are both supported, and it is easy to establish a secure infrastructure model at any complexity level from the many templates available from CloudFormation.</p><p><strong>3.</strong> <strong>Terraform</strong></p><p>The previous IC Tools we have covered so far designed to work with specific cloud environments. Terraform, developed by HashiCorp, is completely cloud-agnostic and helps you tackle large infrastructure for complex distributed applications, for example, with more ease than working on a cloud-specific platform.</p><p>Terraform automation comes in various shapes and is orchestrated in varying degrees with the focus on the core plan/apply cycle. Some teams run Terraform locally but use wrapper scripts to set up a consistent working directory for Terraform to run in. Other development teams run Terraform entirely within an alternate orchestration tool such as Jenkins. It is by far the most adaptable tool on this list but subsequently potentially intimidating, to begin with at least.</p><p>Terraform also supports the change and provisioning previews, plus it has a capable set of features for replicating deployments and individual server instances. Terraform then also takes it a step further with its version control and remote states which provide a centralized source of truth for remote teams working in collaboration.</p><p>There are many more IaC offerings such as Puppet, Ansible, Chef, and Google Cloud Deployment Manager. Choosing the best IaC tool is a matter of finding one that suits your personal preference and specific needs best.</p><h3><strong>The advantages of infrastructure as code (IAC)</strong></h3><p>· IAC is useful for any organization and any IT team but it best suited for organizations looking to take advantage of new, more responsive approaches to IT, like cloud computing, agile development, and DevOps.</p><p>· IAC tends to promote better quality code than scripting.</p><p>· IAC helps reduce the number of problems caused by misconfigured infrastructure in production and can roll back to a “known good” state if there is a problem in the code.</p><p>· With greater rigor and quality control during development, IAC provides predefined “known good” processes for provisioning, the desired state controls to revert manual or out-of-band changes, etc.,</p><p>· IAC’s benefit is in getting hardware deployed quickly on-premises, in the cloud, and in the fast-growing edge computing — for too many IT shops, that approach is still a new concept.</p><p>· The most notable benefits of IAC compared to prior methods is the speed and agility in not only provisioning and deploying your hardware but in maintaining it as well.</p><p>· By automating the handling of routine processes like building server connections to storage, switches, and so forth, the IT team is freed up for other tasks.</p><p>· This becomes a true necessity in multi-cloud environment. All these clouds have different software-defined APIs. IAC is the best way to abstract yourself away from the underlying heterogeneity of the underlying clouds.</p><p>· we can also use IaC to release Solutions. While the containers consist of all features required to run an application, we would expect it to have linear behavior in multiple environments like the Dev and Prod environments. But, it may not act as expected in different production environments. It requires the same infrastructure configuration across all environments for uniform application behavior.</p><h3><strong>Conclusion</strong></h3><p>The DevOps methodology, as a lifecycle model as well as a software cultural revolution, is here to stay. The winners here will be chosen by their ability to metamorphose before they risk losing relevance.</p><p>DevOps practice is a continuous rigorous approach encompassing every component of the project lifecycle that will enable your organization to not just adopt a mere development model but to rethink the way products are developed.</p><p>Furthermore, when we deploy infrastructure as code in CI/CD pipeline, we no longer have to manually run the deployment of the template instead we could use just commands. We can deploy both changes in microservices infrastructure and containers in the CI/CD release pipeline. This enables complete visibility of both the application code and infrastructure code in the pipeline deployed currently in the production environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3a3e0c20ce7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/infrastructure-as-code-iac-in-devops-ecosystem/infrastructure-as-code-iac-in-devops-and-cloud-ecosystem-d3a3e0c20ce7">Infrastructure as Code (IaC) in DevOps and Cloud ecosystem</a> was originally published in <a href="https://medium.com/infrastructure-as-code-iac-in-devops-ecosystem">Infrastructure as Code(IaC) in DevOps ecosystem</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>