-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roll out AWS managed rabbitmq with replication #283
Comments
Tracked by ITISFoundation/osparc-issues#1018 |
This seems blocked by simcore not being able to handle the |
Blocked until ITISFoundation/osparc-simcore#4567 propagates to staging/prod (it is in Sundae3) |
We use it now in the ZMT deployment. It is in. |
Amazom MQ Cluster deployment for high availability: |
Amazon broker config reference: Terraform
Deployment mode reference: |
|
aws mq Rabbit broker instance types |
A good short article explaining mandatory maintenance of Amazon MQ. It leads to many conclusions like: single instance broker will leave us without rabbit during maintenance. |
replicated RabbitMQ for sim4life.io: |
All the code is merged. It can be closed after next staging and next prod release. |
No description provided.
The text was updated successfully, but these errors were encountered: