<?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>AWS on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/aws/</link><description>Recent content in AWS on Karpoke - Just Another Blog</description><generator>Hugo -- 0.159.0</generator><language>es</language><lastBuildDate>Mon, 07 Nov 2016 00:20:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>The open guide to Amazon Web Services</title><link>http://karpoke.ignaciocano.com/2016/11/07/the-open-guide-to-amazon-web-services/</link><pubDate>Mon, 07 Nov 2016 00:20:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2016/11/07/the-open-guide-to-amazon-web-services/</guid><description>&lt;p&gt;Related:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;A lot of information on AWS is already written. Most people learn AWS by
reading a blog or a “getting started guide” and referring to the standard
AWS references. Nonetheless, trustworthy and practical information and
recommendations aren’t easy to come by. AWS’s own documentation is a
great but sprawling resource few have time to read fully, and it doesn’t
include anything but official facts, so omits experiences of engineers. The
information in blogs or Stack Overflow is also not consistently up to date.&lt;/p&gt;</description></item></channel></rss>