<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Cfn on The IT Hollow</title>
    <link>https://theithollow.com/tags/cfn/</link>
    <description>Recent content in Cfn on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 14 Nov 2018 15:02:55 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/cfn/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using AWS CloudFormation Drift Detection</title>
      <link>https://theithollow.com/2018/11/14/using-aws-cloudformation-drift-detection/</link>
      <pubDate>Wed, 14 Nov 2018 15:02:55 +0000</pubDate>
      <guid>https://theithollow.com/2018/11/14/using-aws-cloudformation-drift-detection/</guid>
      <description>&lt;p&gt;Today, AWS announced the release of the long anticipated drift detection feature for CloudFormation. This feature has been a common feature request for many of the AWS customers that I speak with to ensure their deployments are configured as expected. This post will take you through why this is an important feature and how you can use it.&lt;/p&gt;
&lt;h1 id=&#34;whats-the-big-deal&#34;&gt;Whats the Big Deal?&lt;/h1&gt;
&lt;p&gt;If you&amp;rsquo;re not familiar with it already, CloudFormation is a free service from AWS that lets you describe your infrastructure through a YAML or JSON file and deploy the configuration. Simply define your desired state and CloudFormation will deploy the resources and arrange them so that dependent services are (usually) deployed in the right order. If you&amp;rsquo;re familiar with Ansible, Chef, or Puppet, this concept of a desired state shouldn&amp;rsquo;t be new.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Quality Checking Infrastructure-as-Code</title>
      <link>https://theithollow.com/2018/11/05/quality-checking-infrastructure-as-code/</link>
      <pubDate>Mon, 05 Nov 2018 14:55:55 +0000</pubDate>
      <guid>https://theithollow.com/2018/11/05/quality-checking-infrastructure-as-code/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;ve been doing application development for long, having tools in place to check the health of your code is probably not a new concept. However, if you&amp;rsquo;re jumping into something like Cloud and you&amp;rsquo;ve been an infrastructure engineer, this may be a foreign concept to you. Isn&amp;rsquo;t it bad enough that you&amp;rsquo;ve started learning Git, JSON, YAML, APIs etc on top of your existing skill sets? Well, take some lessons from the application teams and you may well find that you&amp;rsquo;re improving your processes and reducing the technical debt and time to provision infrastructure as code resources as well.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Custom Resources</title>
      <link>https://theithollow.com/2018/09/04/aws-custom-resources/</link>
      <pubDate>Tue, 04 Sep 2018 14:00:04 +0000</pubDate>
      <guid>https://theithollow.com/2018/09/04/aws-custom-resources/</guid>
      <description>&lt;p&gt;We love to use AWS CloudFormation to deploy our environments. Its like configuration management for our AWS infrastructure in the sense that we write a desired state as code and apply it to our environment. But sometimes, there are tasks that we want to complete that aren&amp;rsquo;t part of CloudFormation. For instance, what if we wanted to use CloudFormation to deploy a new account which needs to be done through the CLI, or if we need to return some information to our CloudFormation template before deploying it? Luckily for us we can use a Custom Resource to achieve our goals. This post shows how you can use CloudFormation with a Custom Resource to execute a very basic Lambda function as part of a deployment.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
