<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Deis Archives - Brandon Checketts</title>
	<atom:link href="https://www.brandonchecketts.com/archives/category/deis/feed" rel="self" type="application/rss+xml" />
	<link>https://www.brandonchecketts.com/archives/category/deis</link>
	<description>Web Programming, Linux System Administation, and Entrepreneurship in Athens Georgia</description>
	<lastBuildDate>Fri, 10 Jul 2015 02:17:55 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.1</generator>
	<item>
		<title>Docker Syslog Container for Sending Logs to CloudWatch</title>
		<link>https://www.brandonchecketts.com/archives/docker-syslog-container-for-sending-logs-to-cloudwatch</link>
					<comments>https://www.brandonchecketts.com/archives/docker-syslog-container-for-sending-logs-to-cloudwatch#respond</comments>
		
		<dc:creator><![CDATA[Brandon]]></dc:creator>
		<pubDate>Fri, 10 Jul 2015 02:16:18 +0000</pubDate>
				<category><![CDATA[Amazon APIs]]></category>
		<category><![CDATA[Deis]]></category>
		<category><![CDATA[Linux System Administration]]></category>
		<guid isPermaLink="false">http://www.brandonchecketts.com/?p=591</guid>

					<description><![CDATA[<p>AWS&#8217;s CloudWatch Logs was first available about a year ago, and to my estimation has gone largely unnoticed. The initial iteration was pretty rough, but some recent changes have made it more useful, including the ability to search logs, and generate events for monitoring in CloudWatch from log content. Unfortunately, the Cloudwatch Logs agent just [&#8230;]</p>
<p>The post <a href="https://www.brandonchecketts.com/archives/docker-syslog-container-for-sending-logs-to-cloudwatch">Docker Syslog Container for Sending Logs to CloudWatch</a> appeared first on <a href="https://www.brandonchecketts.com">Brandon Checketts</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><a href="https://aws.amazon.com/cloudwatch/details/#log-monitoring">AWS&#8217;s CloudWatch Logs</a> was first available <a href="https://forums.aws.amazon.com/ann.jspa?annID=2554">about a year ago</a>, and to my estimation has gone largely unnoticed.  The initial iteration was pretty rough, but some recent changes have made it more useful, including the ability to search logs, and generate events for monitoring in CloudWatch from log content.</p>
<p>Unfortunately, the Cloudwatch Logs agent just watches log files on disk and doesn&#8217;t act as a syslog server.  An AWS blog post explained how to get the the <a href="https://blogs.aws.amazon.com/application-management/post/TxFRDMTMILAA8X/Send-ECS-Container-Logs-to-CloudWatch-Logs-for-Centralized-Monitoring">Cloudwatch Logs Agent running inside a container</a> and monitoring the log output from rsyslogd, but the instructions used Amazon&#8217;s ECS service, which still doesn&#8217;t quite offer the flexibility that <a href="https://coreos.com/">CoreOS</a> or <a href="https://deis.io/">Deis</a> offer IMHO.  ECS does some magic behind the scenes in passing credentials around that you have to do yourself when using CoreOS.</p>
<p>I&#8217;ve just provided a <a href="https://github.com/RoundSphere/cloudwatchlogs">GitHub repository</a> with the tools to make this work pretty easily, as well as a <a href="https://registry.hub.docker.com/u/roundsphere/cloudwatchlogs/">Docker Image</a> with some reasonable defaults.</p>
<p>When trying to pull all of this together to work, I discovered a problem due to a <a href="https://github.com/docker/docker/issues/10180">bug in the overlayfs</a> that is in current Deis Releases which causes the AWS Logs agent not to notice changes in the syslog files. A workaround is available that <a href="https://serverfault.com/questions/661454/tail-f-not-following-log-file-in-docker-container/704770#704770">reformats the host OS back to btrfs</a> to solve that particular problem</p>
<p>Note when running on Deis 561+ to revert to btrfs</p>
<p>The post <a href="https://www.brandonchecketts.com/archives/docker-syslog-container-for-sending-logs-to-cloudwatch">Docker Syslog Container for Sending Logs to CloudWatch</a> appeared first on <a href="https://www.brandonchecketts.com">Brandon Checketts</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.brandonchecketts.com/archives/docker-syslog-container-for-sending-logs-to-cloudwatch/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Deis add Key from an ssh-agent</title>
		<link>https://www.brandonchecketts.com/archives/deis-add-key-from-an-ssh-agent</link>
					<comments>https://www.brandonchecketts.com/archives/deis-add-key-from-an-ssh-agent#respond</comments>
		
		<dc:creator><![CDATA[Brandon]]></dc:creator>
		<pubDate>Fri, 03 Jul 2015 21:00:12 +0000</pubDate>
				<category><![CDATA[Deis]]></category>
		<category><![CDATA[Linux System Administration]]></category>
		<guid isPermaLink="false">http://www.brandonchecketts.com/?p=588</guid>

					<description><![CDATA[<p>Evidently it is not possible to add an SSH key directly from an SSH agent. Instead, you can grep the public key from your ~/.ssh/authorized_keys file then, have deis use that key. Or if you only have one line in ~/.ssh/authorized_keys, you can just tell deis to use that file directly with the command deis [&#8230;]</p>
<p>The post <a href="https://www.brandonchecketts.com/archives/deis-add-key-from-an-ssh-agent">Deis add Key from an ssh-agent</a> appeared first on <a href="https://www.brandonchecketts.com">Brandon Checketts</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Evidently it is not possible to add an SSH key directly from an SSH agent.  Instead, you can grep the public key from your ~/.ssh/authorized_keys file then, have deis use that key.  Or if you only have one line in ~/.ssh/authorized_keys, you can just tell deis to use that file directly with the command</p>
<pre class="code">
deis keys:add ~/.ssh/authorized_keys
</pre>
<p>The post <a href="https://www.brandonchecketts.com/archives/deis-add-key-from-an-ssh-agent">Deis add Key from an ssh-agent</a> appeared first on <a href="https://www.brandonchecketts.com">Brandon Checketts</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.brandonchecketts.com/archives/deis-add-key-from-an-ssh-agent/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
