AWS SQS as a broker doesn't seem to seem to receive any messages

[shmcgough]

I have a Flask project using WebSockets, served with Gunicorn and gevent, along with a Celery worker running in a separate container. Both the main Flask app and the Celery worker use Flask-SocketIO, the flask app serves the /socket.io endpoint and triggers most of the websocket interactions and the worker simply needs to send messages to the broker to trigger events.

When using Redis as the message broker, everything works perfectly. However, with SQS, while WebSocket functionality from the main Flask server works fine, messages sent from the worker never appear in the SQS queue. Checking the SQS console and manually polling the queue confirm that no messages are being received.

Has anyone had any luck working with SQS? Its been a real battle for me so far, I've also found no way to overwrite the default queue name, it seems to inherit a hardcoded value of python-websockets-uuid.

Would love any ideas on how to debug this or examine why nothing is actually going to SQS, because if I delete the queue itself, the program crashes and complains the queue doesn't exist, so I don't know why it won't use it for the messages too.

[shmcgough]

As a side note, I have celery itself running on the worker also using sqs as a broker, albeit with a seperate queue and that works just fine.

[miguelgrinberg]

I don't think I have ever tested SQS. This uses Kombu, which is mainly intended to work with RabbitMQ but also supports many other queues including SQS. I may need to set up a test to see what's going on with this if you can't figure it out.

[shmcgough]

I've tried everything I could think of including creating my own kombu instance with predefined_queues and passing that as the client_manager to the socketio constructor. I think it may be just not working, I would be slow to say something like that usually, but I put alot of hours into it and the fact that redis just works and celery using sqs on the same container works I don't know what else it might be. If I figure something out I'll be sure to update.