<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Amazon S3 on Caktus Group</title><link>https://www.caktusgroup.com/tags/Amazon-S3/</link><description>Recent content in Amazon S3 on Caktus Group</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 10 Nov 2014 16:28:11 +0000</lastBuildDate><atom:link href="https://www.caktusgroup.com/tags/Amazon-S3/index.xml" rel="self" type="application/rss+xml"/><item><title>Using Amazon S3 to Store your Django Site's Static and Media Files</title><link>https://www.caktusgroup.com/blog/2014/11/10/Using-Amazon-S3-to-store-your-Django-sites-static-and-media-files/</link><pubDate>Mon, 10 Nov 2014 16:28:11 +0000</pubDate><guid>https://www.caktusgroup.com/blog/2014/11/10/Using-Amazon-S3-to-store-your-Django-sites-static-and-media-files/</guid><description>&lt;p>&lt;em>Editor's note: This post was updated in September 2017.&lt;/em>&lt;/p>
&lt;h2 id="using-amazon-s3-to-store-your-django-sites-static-and-media-files">Using Amazon S3 to Store your Django Site's Static and Media Files&lt;/h2>
&lt;p>Storing your Django site's static and media files on Amazon S3, instead
of serving them yourself, can improve site performance. It frees your
servers from handling static files themselves, lets you scale your
servers easier by keeping media files in a common place, and is a
necessary step to using Amazon CloudFront as a Content Delivery Network
(CDN).&lt;/p></description></item><item><title>Using Django and Celery with Amazon SQS</title><link>https://www.caktusgroup.com/blog/2011/12/19/using-django-and-celery-amazon-sqs/</link><pubDate>Mon, 19 Dec 2011 16:26:48 +0000</pubDate><guid>https://www.caktusgroup.com/blog/2011/12/19/using-django-and-celery-amazon-sqs/</guid><description>&lt;p>Amazon's &lt;a href="http://aws.amazon.com/sqs/" target="_blank" rel="noopener noreferrer">Simple Queue Service&lt;/a> (SQS) is a
relatively new offering in the family of Amazon Web Services (AWS).
It's also an appealing one, because it proposes to quickly and easily
replace a common component of the stack in a typical web application,
thereby obviating the need to run a separate queue server like
&lt;a href="http://www.rabbitmq.com/" target="_blank" rel="noopener noreferrer">RabbitMQ&lt;/a>. While RabbitMQ &amp;mdash; the typical
favorite for Celery users &amp;mdash; is not necessarily difficult to install or
maintain, removing it from the stack of a web application means one less
component that might fail, offloading that service to AWS &amp;mdash; especially
for applications with a small to moderate queue volume &amp;mdash; might prove
financially advantageous.&lt;/p></description></item></channel></rss>