<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AWS on Nyghtowl</title>
    <link>https://nyghtowl.com/tags/aws/</link>
    <description>Recent content in AWS on Nyghtowl</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>&lt;a href=&#34;https://creativecommons.org/licenses/by-nc-sa/4.0/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CC BY-NC-SA 4.0&lt;/a&gt;</copyright>
    <lastBuildDate>Mon, 07 Jul 2014 22:45:32 +0000</lastBuildDate>
    <atom:link href="https://nyghtowl.com/tags/aws/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MapReduce, MRJob &amp; AWS EMR Pointers</title>
      <link>https://nyghtowl.com/posts/2014/07/mapreduce-mrjob-aws-emr-pointers/</link>
      <pubDate>Mon, 07 Jul 2014 22:45:32 +0000</pubDate>
      <guid>https://nyghtowl.com/posts/2014/07/mapreduce-mrjob-aws-emr-pointers/</guid>
      <description>&lt;p&gt;Over the last couple weeks, I’ve been playing around with MapReduce, MRJob and AWS to answer some questions about event data. Granted this is definitely more data engineering focused than data science, but using these tools can be very beneficial if you are analyzing a ton of data (esp. event log data).&lt;/p&gt;&#xA;&lt;p&gt;This is more of an overview with a few lessons learned on how to setup a MapReduce job using MRJob and AWS EMR. This post focuses more on process and less about the script logic.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
