Need help using RabbitMQ with SSL #1903
-
Shlink version3.10.2 PHP versionDocker image How do you serve ShlinkRoadRunner Docker image Database engineMySQL Database version8.0.0 SummaryI'm using AWS RabbitMQ, which comes with default SSL. I have configured the correct values in the environment, and the events are not getting published to MQ. When I locally test with RabbitMQ without SSL, it works as expected. I'm wondering if I need to be more accurate in the setup in the Cloud or if Shlink does not support RabbitMQ with SSL. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 2 replies
-
I'm sharing more information about the Setup. I deployed |
Beta Was this translation helpful? Give feedback.
-
I also wrote a separate consumer application that connects with the same RabbitMQ configured to Shlink - also deployed as an ECS Fargate Service. The consumer application can connect to the MQ broker and listen to the Queue. So, I know the MQ configurations are working as expected, and there is no trouble with the networking. |
Beta Was this translation helpful? Give feedback.
-
I'm using the Container - |
Beta Was this translation helpful? Give feedback.
-
@acelaya - could you let me know the answer to this question? |
Beta Was this translation helpful? Give feedback.
-
EDIT 2023-11-25: Shlink 3.7.0 now supports encrypted RabbitMQ connections via TLS. By taking a quick look at the options used by the AMQP abstraction library that Shlink uses, it seems there's some extra config needed in order to support connections over SSL. With that considered, plus the fact that it was never tested, I'm almost sure it is not currently possible without changes in Shlink's implementation. I've created an issue to track this: #1906 |
Beta Was this translation helpful? Give feedback.
-
Thank you, @acelaya, for your response and the created issue. 🙏🏾 |
Beta Was this translation helpful? Give feedback.
EDIT 2023-11-25: Shlink 3.7.0 now supports encrypted RabbitMQ connections via TLS.
By taking a quick look at the options used by the AMQP abstraction library that Shlink uses, it seems there's some extra config needed in order to support connections over SSL.
With that considered, plus the fact that it was never tested, I'm almost sure it is not currently possible without changes in Shlink's implementation.
I've created an issue to track this: #1906