<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud on Tate Eskew</title><link>http://tateeskew.com/tags/cloud/</link><description>Recent content in Cloud on Tate Eskew</description><generator>Hugo</generator><language>en-us</language><copyright>Tate Eskew</copyright><lastBuildDate>Wed, 06 Mar 2013 06:11:27 +0000</lastBuildDate><atom:link href="http://tateeskew.com/tags/cloud/index.xml" rel="self" type="application/rss+xml"/><item><title>Automating Dynamic DNS updating with AWS Instances and Route53</title><link>http://tateeskew.com/weblog/2013-03-06-automating-dynamic-dns-updating-with-aws-instances-and-route53/</link><pubDate>Wed, 06 Mar 2013 06:11:27 +0000</pubDate><guid>http://tateeskew.com/weblog/2013-03-06-automating-dynamic-dns-updating-with-aws-instances-and-route53/</guid><description>&lt;p&gt;&lt;strong&gt;UPDATE&lt;/strong&gt;: This information is long out of date. With the release of the awscli toolset in pypi years ago, things have changed a bit. Also, Amazon is forcing you to VPC on new accounts (years ago now). I will not be updating this post, but maybe you can find something useful here.&lt;/p&gt;
&lt;p&gt;&lt;span class="largestartfont"&gt;R&lt;/span&gt;ecently I&amp;rsquo;ve been building the underlying system platform for the development of our distributed application on AWS. We do a lot of clustering using &lt;a href="http://storm-project.net/"&gt;Storm&lt;/a&gt; and &lt;a href="http://hadoop.apache.org/"&gt;Hadoop&lt;/a&gt;, which means that we sometimes spin up hundreds of instances that may only live for a few hours during a run. Getting metrics, logs and all of those &amp;lsquo;must-haves&amp;rsquo; centralized has been part of this build-out. When working with large amounts of machines in short-lived clusters, it becomes a real pain in the ass to use the built-in DNS/naming mechanism/scheme that AWS provides by default. Everything starts to look the same inside of your reporting/metrics/monitoring tools when working with the arbitrary names given to the instances. Hence, this article.&lt;/p&gt;</description></item></channel></rss>