<?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 Chris Ramsay</title><link>https://chrisramsay.co.uk/tag/aws/</link><description>Recent content in Aws on Chris Ramsay</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><copyright>© Chris Ramsay. Content CC BY-NC-SA 4.0 unless stated otherwise.</copyright><lastBuildDate>Wed, 16 Nov 2016 00:00:00 +0000</lastBuildDate><atom:link href="https://chrisramsay.co.uk/tag/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>Creating AWS Data Pipelines with Boto3 and JSON</title><link>https://chrisramsay.co.uk/posts/2016/11/creating-aws-data-pipelines-with-boto3-and-json/</link><pubDate>Wed, 16 Nov 2016 00:00:00 +0000</pubDate><guid>https://chrisramsay.co.uk/posts/2016/11/creating-aws-data-pipelines-with-boto3-and-json/</guid><description>I have been doing a little work with AWS data pipeline recently for undertaking ETL tasks at work. AWS data pipeline handles data driven workflows called pipelines. The data pipelines take care of scheduling, data depenedencies, data sources and destinations in a nicely managed workflow. My tasks take batch datasets from SQL databases, processing and…</description></item></channel></rss>