Amazon provides a Simple Queuing Service (SQS): http://aws.amazon.com/sqs/ Socorro should support this as an alternative to RabbitMQ, so we have fewer services that we need to support ourselves.

As far as I understand it, Amazon SQS is not a free software that our external users could use on their own installs, so I just wanted to make sure that we will keep supporting RabbitMQ (I don't think we want to force users of Socorro to run on Amazon). Maybe I'm stating the obvious, but I feel better this way. :)

(In reply to Adrian Gaudebert [:adrian] from comment #1) > As far as I understand it, Amazon SQS is not a free software that our > external users could use on their own installs, so I just wanted to make > sure that we will keep supporting RabbitMQ (I don't think we want to force > users of Socorro to run on Amazon). > > Maybe I'm stating the obvious, but I feel better this way. :) Not planning on removing RabbitMQ (see also https://groups.google.com/forum/#!topic/mozilla.tools.socorro/QN6pz2BzIUU specifically "We plan to continue supporting RabbitMQ as a queue and filesystem as long-term storage, though we will likely be using SQS and S3 respectively in production, so these will be options for those who do not run Socorro in AWS."). It's important to be able to run Socorro outside of AWS for non-Mozilla installs, local development, and just to stay flexible in case we want to switch to another cloud provider.

Not currently working on this - I did some exploratory work and I think it'd be pretty straightforward to add a class in the style of the RabbitMQ crash storage that supports AWS SQS. I haven't tried to estimate the cost difference, but not having to administer a Rabbit cluster has to be worth something ;)

We have no active plans on the infrastructure side to move to SQS, though it's definitely an interesting idea that we've discussed at points. Unblocking the tracker bug for optimizing AWS (that I'm resolving).

We have no plans to do this (still), so I'm going to mark it as WONTFIX. If we decide to switch, we can open up a new bug then with details.