<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>EC2 on iMil.net</title>
    <link>http://imil.net/blog/tags/ec2/</link>
    <description>Recent content in EC2 on iMil.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 05 Aug 2016 14:07:00 +0000</lastBuildDate>
    <atom:link href="http://imil.net/blog/tags/ec2/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Ansible and AWS ASG, a (really) dynamic inventory</title>
      <link>http://imil.net/blog/posts/2016/ansible_and_aws_asg/</link>
      <pubDate>Fri, 05 Aug 2016 14:07:00 +0000</pubDate>
      <guid>http://imil.net/blog/posts/2016/ansible_and_aws_asg/</guid>
      <description>&lt;p&gt;I found myself searching ridiculously too long to achieve what I believed was a simple task: to apply an &lt;a href=&#34;http://www.ansible.com&#34;&gt;Ansible&lt;/a&gt; &lt;em&gt;role&lt;/em&gt; to newly created  instances&amp;hellip; started by an &lt;a href=&#34;https://aws.amazon.com/autoscaling/&#34;&gt;Auto Scaling Group&lt;/a&gt;. If you&amp;rsquo;re used to &lt;a href=&#34;http://www.ansible.com&#34;&gt;Ansible&lt;/a&gt; you know that it relies on an &lt;em&gt;inventory&lt;/em&gt; to apply a &lt;code&gt;playbook&lt;/code&gt;, but obviously, when you&amp;rsquo;re firing up &lt;em&gt;EC2&lt;/em&gt; instances with the same &lt;code&gt;playbook&lt;/code&gt;, you are not able to know what will be your virtual machines IP addresses, nor can &lt;a href=&#34;http://docs.ansible.com/ansible/intro_dynamic_inventory.html&#34;&gt;ec2.py&lt;/a&gt;, the recommended method to deal with dynamic inventories.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
