<?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 Solutr.com</title>
    <link>https://solutr.com/tags/aws/</link>
    <description>Recent content in Aws on Solutr.com</description>
    <image>
      <title>Solutr.com</title>
      <url>https://solutr.com/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://solutr.com/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.147.9</generator>
    <language>en</language>
    <lastBuildDate>Fri, 13 May 2016 18:23:00 +0200</lastBuildDate>
    <atom:link href="https://solutr.com/tags/aws/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>S3 API too slow? xargs to the rescue.</title>
      <link>https://solutr.com/posts/2016-05-13-s3-api-too-slow-xargs-to-the-rescue/</link>
      <pubDate>Fri, 13 May 2016 18:23:00 +0200</pubDate>
      <guid>https://solutr.com/posts/2016-05-13-s3-api-too-slow-xargs-to-the-rescue/</guid>
      <description>&lt;p&gt;My days as a BigData engineer grew darker in the past few days. Now
almost all critical data that our aggregations, partners and customers
want to access is located in a bucket on Amazon&amp;rsquo;s S3. Since that gets
horribly expensive for the vast amounts of data we create on a daily
basis, we lean towards not keeping much more than a month of active
objects in the bucket, to meet our SLA&amp;rsquo;s regarding backup and recovery,
we keep them for about a year in Glacier afterwards.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
