Added support for SQS fanout via AWS SNS

README.rst

@@ -70,6 +70,7 @@ and the `Wikipedia article about AMQP`_.
 .. _`Pyro`: https://pyro4.readthedocs.io/
 .. _`SoftLayer MQ`: https://sldn.softlayer.com/reference/messagequeueapi
 .. _`MongoDB`: https://www.mongodb.com/
+.. _`AWS SNS`: https://aws.amazon.com/sns/
 
 .. _transport-comparison:
 
@@ -102,9 +103,9 @@ Transport Comparison
 .. [#f1] Declarations only kept in memory, so exchanges/queues
          must be declared by all clients that needs them.
 
-.. [#f2] Fanout supported via storing routing tables in SimpleDB.
-         Disabled by default, but can be enabled by using the
-         ``supports_fanout`` transport option.
+.. [#f2] Fanout is supported via `AWS SNS`_. A notification is sent to SNS, and a copy is set to all subscribed
+         `Amazon SQS`_ queues. Please consult the AWS SNS and SQS pricing pages to see how this will affect your usage
+         costs. Disabled by default, but can be enabled by using the ``supports_fanout`` transport option.
 
 .. [#f3] AMQP Message priority support depends on broker implementation.
 

docs/reference/kombu.transport.SQS.rst

@@ -23,6 +23,7 @@
         :members:
         :undoc-members:
 
+
 Back-off policy
 ------------------------
 Back-off policy is using SQS visibility timeout mechanism altering the time difference between task retries.
@@ -70,4 +71,22 @@ Message Attributes
 
 SQS supports sending message attributes along with the message body.
 To use this feature, you can pass a 'message_attributes' as keyword argument
-to `basic_publish` method.
+to `basic_publish` method.
+
+
+Amazon SQS Transport - ``kombu.transport.SQS.exceptions``
+================================================
+
+.. automodule:: kombu.transport.SQS.exceptions
+   :members:
+   :show-inheritance:
+   :undoc-members:
+
+
+Amazon SQS Transport - ``kombu.transport.SQS.SNS``
+================================================
+
+.. automodule:: kombu.transport.SQS.SNS
+   :members:
+   :show-inheritance:
+   :undoc-members: